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

Output: Week


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

Output: Time


Input: [Keyword] datetime-local [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 [State]

Output: Local Date and Time


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

Output: Number


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

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


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

Output: File Upload


Input: [Keyword] submit [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 [State]

Output: Submit Button


Input: [Keyword] image [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 [State]

Output: Image Button


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

Output: Reset Button


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

Output: Button


Input: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a Dialog URL [Description] An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter should prepare. [Name]

Output: src

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description] An 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. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files. [Name]

Output: type

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of one or more whitespace separated CCXML variable names. These variables will be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value is first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute will receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of dialogstart, dialogterminate, join, or unjoin. [Name]

Output: dialogid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Can not be used with conferenceid [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description] An Optional ECMAScript expression which returns the identifier of a connection. The specified connection will be associated with the dialog being prepared. If the attribute value is invalid, an error.semantic event will be thrown. [Name]

Output: connectionid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Can not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description] An Optional ECMAScript expression which returns the identifier of`a confe2ence bridge. A connection will be allocated for the dialog being prepared. If the attribute value is invalid, an error.semantic event will be thrown. [Name]

Output: conferenceid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description] An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference specified by the connectionid or conferenceid attribute. The following values can be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent dialogstart is executed, but this attribute can be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment should make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 . [Name]

Output: mediadirection

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned is interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Name]

Output: maxage

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned is interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Name]

Output: maxstale

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist will be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method will be used by the dialog manager. post This indicates that the "POST" method will be used by the dialog manager. [Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] name [Optional] false [Definitions]

Output: This property is set to the ECMAScript string value of the event name.

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connectionid [Optional] false [Definitions]

Output: This property is the ECMAScript string value of the ID of the Connection object associated with this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] protocol [Optional] true [Definitions]

Output: This property is an ECMAScript string which identifies the protocol used by the event source; although this property is OPTIONAL, it is recommended that platforms provide it in order to allow applications to tailor their behavior (see Appendix E for a suggested set of protocol identifiers)

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] info [Optional] true [Definitions]

Output: This property provides a reference to an object which MAY contain platform or protocol dependent information specific to the event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] reason [Optional] true [Definitions]

Output: This property, although not provided by every event, when present provides a code indicating the status of the operation which triggered this event, or a reason for the occurrence of this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connection [Optional] false [Definitions]

Output: An ECMAScript object reference to the Connection object identified by the connectionid property for this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [XKMS element] Message/Service [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Request/Signature [Required]

Output: Optional, may be used to support non-repudiation

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Response/Signature [Required]

Output: Optional, may be used to support non-repudiation

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Message/RequestID [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Message/ResponseID [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Message/Nonce [Required]

Output: Unnecessary

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Request/RespondWith=Represent [Required]

Output: Unnecessary

XML Key Management Specification (XKMS) Part II


Input: [XKMS element] Request/MessageHash [Required]

Output: Unnecessary

XML Key Management Specification (XKMS) Part II


Input: any atompub server exposes a "service document" (http://tools.ietf.org/html/rfc5023#section-8) that describes what the server is exposing. each service document lists a set of "workspaces" (http://tools.ietf.org/html/rfc5023#section-8.1), which are just a grouping construct for "collections". workspaces have no interaction semantics in atompub, there is no protocol for creating or deleting them; they just exist. each workspace lists a set of "collections" (http://tools.ietf.org/html/rfc5023#section-10), which is by far the most central construct in atompub. a collection can be listed in more than one workspace. [Model Aspect]

Output: service basics

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: a collection has a URI where you can start interacting with the collection, at the most basic level you can GET a list of members (http://tools.ietf.org/html/rfc5023#section-10), and very likely this is somehow paginated (http://tools.ietf.org/html/rfc5023#section-10.1). through its listing in a service document, the collection exposes some interaction information, such as which kind of mediatypes it will accept (http://tools.ietf.org/html/rfc5023#section-8.3.4), and how members of the collection might use categories (http://tools.ietf.org/html/rfc5023#section-8.3.6) to be classified. [Model Aspect]

Output: collection basics

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: any kind of resource can be listed in a collection (http://tools.ietf.org/html/rfc5023#section-4.2), and everything that is in a collection is represented by an entry. entries follow the standardized metadata model defined by atom (http://tools.ietf.org/html/rfc4287), but atompub distinguishes two kinds of entries. if a client POSTs an "entry resource" (an atom entry following atom's metadata model), the server pretty much takes this entry resource and starts listing it in the collection as a member. if a client has POSTed a "media resource" (pretty much anything that's not an entry by itself, often something like an image media type), which has to be in one of the accepted media types of the collection, the server accepts this media resource and creates a "media link entry", which will then represent this media resource when you list the collection contents. servers might try to be smart about populating metadata fields in the entry and for example look at exif data to populate certain fields. the interesting aspect of this setup is that you POST one thing, and create two resources (http://tools.ietf.org/html/rfc5023#section-9.6), and big media files might for example get added to a CDN and get a CDN URI, whereas the entry gets some URI under the control of the atompub server. [Model Aspect]

Output: creating collection members

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: a collection is a representation of members, and thus contains a list of entries representing each individual member. according to the atom model, each entry MUST have an http://tools.ietf.org/html/rfc4287#section-4.2.6, which is a URI but has no interaction semantics (specifically, best practice suggests that minting URIs that are not actionable might be a good idea http://web.archive.org/web/20110514113830/http://diveintomark.org/archives/ 2004/05/28/howto-atom-id). entries may have embedded content, or may link to the content they are representing (http://tools.ietf.org/html/rfc4287#section-4.1.3). identity is established by the entry , and this is particularly important in scenarios where collections may be aggregated and filtered and repurposed: entry identity must always be visible in the , and thus identity can be tracked across paths where entries may get repurposed in various collections. [Model Aspect]

Output: member identity

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: members are listed when GETting a collection, and their identity and metadata about them is exposed through regular atom mechanisms. if members are editable, an "edit" link in the entry (http://tools.ietf.org/html/rfc5023#section-11.1) will allow clients to update the member entry, by using this link to PUT or DELETE the entry resource. if the entry is a media link entry, then there might be a "edit-media" link in the entry (http://tools.ietf.org/html/rfc5023#section-11), which will allow clients to update the media resource, by using this link to PUT or DELETE the media resource. this model allows clients to both interact with a media resource's metadata (the "media link entry"), and the media resource itself. [Model Aspect]

Output: interacting with members

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: like workspaces, collections just exist, and atompub does not define how to create or delete them (i am currently working on a small addition to the spec that addresses that). also, collections have no structure, they have a URI and accept entries. this means there is no hierarchy to collections, it's a flat space. [Model Aspect]

Output: interacting with collections

Difference between revisions of "ISSUE-37" - Linked Data Platform


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: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a Dialog URI [Description] An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter must prepare. [Name]

Output: src

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description] An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/x-wav This MIME type would request a dialog manager that merely plays wave files. [Name]

Output: type

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of one or more whitespace separated CCXML variable names. These variables are sent to the dialog environment as a list of name/value pairs. Names are sent exactly as they are specified; values are formed by converting the referenced ECMAScript variable to string form (which is undefined for objects). The dialog environment determines how passed parameters will be handled [Name]

Output: parameters

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. If the attribute value is invalid, an error.semantic event MUST be thrown [Name]

Output: dialogid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Must not be used with conferenceid [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description] An Optional ECMAScript expression which returns the identifier of a connection. If specified, the dialog being prepared MUST be joined to the referenced connection as specified by the mediadirection attribute. Note that if the referenced connection is already bridged to another media endpoint, those existing bridges may be affected according to the rules specified in section 10.4 even prior to being performed If the attribute value is invalid an error.semantic event must be thrown. [Name]

Output: connectionid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Must not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description] An Optional ECMAScript expression which returns the identifier of a conference bridge. If specified, the dialog being prepared MUST be joined to the referenced conference as specified by the mediadirection attribute. If the attribute value is invalid an error.semantic event must be thrown. [Name]

Output: conferenceid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description] An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent is executed, but this attribute may be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment must make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 . [Name]

Output: mediadirection

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616] ). The document is not willing to use stale content, unless maxstale is also provided. [Name]

Output: maxage

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616] ). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Name]

Output: maxstale

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Valid only when the value of the method is "post" , otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager. [Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description] The ECMAScript object returned contains information which may be used by the implementing platform for implementing the dialog operation. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform. [Name]

Output: hints

Voice Browser Call Control: CCXML Version 1.0


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: UIEvent


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

Output: MutationEvent


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

Output: MutationEvent


Input: [Event Type] DOMFocusIn [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Window, Element [Cancelable] No [Default Action] None [DOM interface]

Output: FocusEvent


Input: [Event Type] DOMFocusOut [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Window, Element [Cancelable] No [Default Action] None [DOM interface]

Output: FocusEvent


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

Output: MutationEvent


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

Output: MutationEvent


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

Output: MutationEvent


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

Output: MutationEvent


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

Output: MutationEvent


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

Output: KeyboardEvent


Input: [Description] The CCXML document answers an incoming call. [Event] connection.connected [End State]

Output: CONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document rejects an incoming call. [Event] connection.failed [End State]

Output: FAILED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document redirects an incoming call. [Event] connection.redirected [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document merges an incoming/connected call with another call at the network level. [Event] connection.merged [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.alerting [Description] Network provided call progress update. [Event] connection.alerting [End State]

Output: ALERTING

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.failed [Description] There was an error in the call state. [Event] connection.failed [End State]

Output: FAILED

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.signal [Description] Additional Connection related information is available for processing by the CCXML application. [Event] connection.signal [End State]

Output: ALERTING

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] error.connection [Description] The CCXML connection had a platform operational error. [Event] error.connection [End State]

Output: ERROR

Voice Browser Call Control: CCXML Version 1.0


Input: [Identifier] Agreement [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former. [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


Input: [Identifier] Offer [Comment] Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party. [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Request [Comment] Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party. [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Ticket [Comment] May contain the Party entity with Assigner role and the Party entity with Assignee role. A Ticket (or Voucher) may be anonymous or personalised, where the holder of that Ticket may remain unknown or has to be identified. The holder, or if known, the Assignee, is being granted the terms of the Ticket from the Assigner (in known). [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [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: [Group] ISOAMSA [Descriptive Name] Added Math Symbols: Arrows [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOAMSB [Descriptive Name] Added Math Symbols: Binary Operators [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOAMSC [Descriptive Name] Added Math Symbols: Delimiters [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOAMSN [Descriptive Name] Added Math Symbols: Negated Relations [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOAMSO [Descriptive Name] Added Math Symbols: Ordinary [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOAMSR [Descriptive Name] Added Math Symbols: Relations [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOTECH [Descriptive Name] General Technical [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOPUB [Descriptive Name] Publishing [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISODIA [Descriptive Name] Diacritical Marks [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISONUM [Descriptive Name] Numeric and Special Graphic [3] Glyphs | [4] Basic [5] Glyphs [2]

Output: Extended


Input: [Group] ISOBOX [Descriptive Name] Box and Line Drawing [3] Glyphs [2]

Output: Basic


Input: [Group] MMALIAS [Descriptive Name] MathML Aliases [3] Glyphs [2]

Output: Basic


Input: [Group] MMEXTRA [Descriptive Name] MathML Additions [3] Glyphs [2]

Output: Basic


Input: [Event] connection.connected [End State] CONNECTED [Description]

Output: The CCXML document answers an incoming call.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.failed [End State] FAILED [Description]

Output: The CCXML document rejects an incoming call.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.redirected [End State] DISCONNECTED [Description]

Output: The CCXML document redirects an incoming call.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.merged [End State] DISCONNECTED [Description]

Output: The CCXML document merges an incoming/connected call with another call at the network level.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.alerting [Event] connection.alerting [End State] ALERTING [Description]

Output: Network provided call progress update.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.failed [Event] connection.failed [End State] FAILED [Description]

Output: There was an error in the call state.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.signal [Event] connection.signal [End State] ALERTING [Description]

Output: Additional Connection related information is available for processing by the CCXML application.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] error.connection [Event] error.connection [End State] ERROR [Description]

Output: The CCXML connection had a platform operational error.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] src [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a Dialog URI [Description]

Output: An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter must prepare.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description]

Output: An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/x-wav This MIME type would request a dialog manager that merely plays wave files.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] parameters [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of one or more whitespace separated CCXML variable names. These variables are sent to the dialog environment as a list of name/value pairs. Names are sent exactly as they are specified; values are formed by converting the referenced ECMAScript variable to string form (which is undefined for objects). The dialog environment determines how passed parameters will be handled

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. If the attribute value is invalid, an error.semantic event MUST be thrown

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Attribute Constraints] Must not be used with conferenceid [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a connection. If specified, the dialog being prepared MUST be joined to the referenced connection as specified by the mediadirection attribute. Note that if the referenced connection is already bridged to another media endpoint, those existing bridges may be affected according to the rules specified in section 10.4 even prior to being performed If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] conferenceid [Required] false [Attribute Constraints] Must not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a conference bridge. If specified, the dialog being prepared MUST be joined to the referenced conference as specified by the mediadirection attribute. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent is executed, but this attribute may be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment must make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 .

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616] ). The document is not willing to use stale content, unless maxstale is also provided.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616] ). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" , otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform for implementing the dialog operation. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] must evaluate to a valid URI [Description] An ECMAScript expression which returns the URI of the resource to be fetched. [Name]

Output: next

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] In processed mode "application/ccxml+xml". In raw mode "*/*". [Valid Values] MIME Types formatted as per HTTP Accept header [RFC2616] [Description] An ECMAScript expression which returns a character string setting the value of the HTTP Accept header to tell the application server what content type the application wishes to have returned. [Name]

Output: type

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it must be submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used to fetch the URI post This indicates that the "POST" method must be used while submitting the URI to the web server. [Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive 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 identifier can be acquired from the fetch completion event. Every fetch request must receive a unique fetch identifier, even if the request is for the same URI [Name]

Output: fetchid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description] The character string returned must be interpreted as a time interval. This interval begins when the fetch is executed. The fetch must fail if not completed at the end of this interval. A failed fetch must return the error.fetch event. [Name]

Output: timeout

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age must be no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616] ). The document is not willing to use stale content, unless maxstale is also provided. [Name]

Output: maxage

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616] ). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Name]

Output: maxstale

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Valid only when the value of the method is "post" , otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] processed [Valid Values] processed, raw [Description] Controls what the CCXML platform should do with fetched content. If set to processed (the default) the CCXML platform MUST attempt to parse and validate the returned content. If set to raw the platform MUST NOT attempt to process the data and MUST leave processing of the content to the application who can do what it wishes with the content via the content attribute of the fetch.done event [Name]

Output: mode

Voice Browser Call Control: CCXML Version 1.0


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

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Model Aspect] service basics

Output: any atompub server exposes a "service document" (http://tools.ietf.org/html/rfc5023#section-8) that describes what the server is exposing. each service document lists a set of "workspaces" (http://tools.ietf.org/html/rfc5023#section-8.1), which are just a grouping construct for "collections". workspaces have no interaction semantics in atompub, there is no protocol for creating or deleting them; they just exist. each workspace lists a set of "collections" (http://tools.ietf.org/html/rfc5023#section-10), which is by far the most central construct in atompub. a collection can be listed in more than one workspace.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] collection basics

Output: a collection has a URI where you can start interacting with the collection, at the most basic level you can GET a list of members (http://tools.ietf.org/html/rfc5023#section-10), and very likely this is somehow paginated (http://tools.ietf.org/html/rfc5023#section-10.1). through its listing in a service document, the collection exposes some interaction information, such as which kind of mediatypes it will accept (http://tools.ietf.org/html/rfc5023#section-8.3.4), and how members of the collection might use categories (http://tools.ietf.org/html/rfc5023#section-8.3.6) to be classified.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] creating collection members

Output: any kind of resource can be listed in a collection (http://tools.ietf.org/html/rfc5023#section-4.2), and everything that is in a collection is represented by an entry. entries follow the standardized metadata model defined by atom (http://tools.ietf.org/html/rfc4287), but atompub distinguishes two kinds of entries. if a client POSTs an "entry resource" (an atom entry following atom's metadata model), the server pretty much takes this entry resource and starts listing it in the collection as a member. if a client has POSTed a "media resource" (pretty much anything that's not an entry by itself, often something like an image media type), which has to be in one of the accepted media types of the collection, the server accepts this media resource and creates a "media link entry", which will then represent this media resource when you list the collection contents. servers might try to be smart about populating metadata fields in the entry and for example look at exif data to populate certain fields. the interesting aspect of this setup is that you POST one thing, and create two resources (http://tools.ietf.org/html/rfc5023#section-9.6), and big media files might for example get added to a CDN and get a CDN URI, whereas the entry gets some URI under the control of the atompub server.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] member identity

Output: a collection is a representation of members, and thus contains a list of entries representing each individual member. according to the atom model, each entry MUST have an http://tools.ietf.org/html/rfc4287#section-4.2.6, which is a URI but has no interaction semantics (specifically, best practice suggests that minting URIs that are not actionable might be a good idea http://web.archive.org/web/20110514113830/http://diveintomark.org/archives/ 2004/05/28/howto-atom-id). entries may have embedded content, or may link to the content they are representing (http://tools.ietf.org/html/rfc4287#section-4.1.3). identity is established by the entry , and this is particularly important in scenarios where collections may be aggregated and filtered and repurposed: entry identity must always be visible in the , and thus identity can be tracked across paths where entries may get repurposed in various collections.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] interacting with members

Output: members are listed when GETting a collection, and their identity and metadata about them is exposed through regular atom mechanisms. if members are editable, an "edit" link in the entry (http://tools.ietf.org/html/rfc5023#section-11.1) will allow clients to update the member entry, by using this link to PUT or DELETE the entry resource. if the entry is a media link entry, then there might be a "edit-media" link in the entry (http://tools.ietf.org/html/rfc5023#section-11), which will allow clients to update the media resource, by using this link to PUT or DELETE the media resource. this model allows clients to both interact with a media resource's metadata (the "media link entry"), and the media resource itself.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] interacting with collections

Output: like workspaces, collections just exist, and atompub does not define how to create or delete them (i am currently working on a small addition to the spec that addresses that). also, collections have no structure, they have a URI and accept entries. this means there is no hierarchy to collections, it's a flat space.

Difference between revisions of "ISSUE-37" - Linked Data Platform


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid target URL [Description]

Output: An ECMAScript expression returning the target location of the event. The target attribute specifies the unique identifier of the event target that the Event I/O Processor should send the event to.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Valid Values] ccxml dialog [Description]

Output: An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event should be dispatched to. Values defined by the specification are: ccxml This species that the event will be dispatched to the CCXML Session Event Processor.. dialog This species that the event will be dispatched to the Dialog Event Processor..

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute will receive an internally generated unique string identifier to be associated with the event being sent. If this attribute is not specified, the event identifier is dropped.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] xmlns:[YourNameSpacePrefix] [Required] false [Type] string [Default Value] none [Description]

Output: This returns a namespace identifying the contained message format. More than one xmlns attribute may be included.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] data [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with inline content [Type] ECMAScript Expression [Default Value] none [Description]

Output: An ECMAScript expression which returns a character string that indicates the type of event being generated. The event type may include alphanumeric characters and the "." (dot) character. The first character may not be a dot or a digit. Event type names are case-insensitive. If neither the data attribute or inline content is specified, an error.fetch event will be thrown. If used in conjunction with the inline content, an error.fetch will be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with inline content [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names to be included with the event. When an ECMAscript variable is included with the event, its value is first converted into a string. If the variable is an ECMAScript Object, the mechanism by which it is included is not currently defined. Instead of including ECMAScript Objects directly, the application developer may explicitly include the properties of an Object. e.g. "date.month date.year". If used in conjunction with the inline content, an error.fetch will be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform to configure the event processor. The meaning of these hints is specific to the implementing platform and the event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event name] loadstart [Dispatched when...]

Output: The user agent begins looking for media data, as part of the resource selection algorithm.


Input: [Event name] progress [Dispatched when...]

Output: The user agent is fetching media data.


Input: [Event name] suspend [Dispatched when...]

Output: The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.


Input: [Event name] abort [Dispatched when...]

Output: The user agent stops fetching the media data before it is completely downloaded, but not due to an error.


Input: [Event name] error [Dispatched when...]

Output: An error occurs while fetching the media data.


Input: [Event name] emptied [Dispatched when...]

Output: A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running).


Input: [Event name] stalled [Dispatched when...]

Output: The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.


Input: [Event name] play [Dispatched when...]

Output: Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin.


Input: [Event name] pause [Dispatched when...]

Output: Playback has been paused. Fired after the pause() method has returned.


Input: [Event name] loadedmetadata [Dispatched when...]

Output: The user agent has just determined the duration and dimensions of the media resource


Input: [Event name] loadeddata [Dispatched when...]

Output: The user agent can render the media data at the current playback position for the first time.


Input: [Event name] waiting [Dispatched when...]

Output: Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.


Input: [Event name] playing [Dispatched when...]

Output: Playback has started.


Input: [Event name] canplay [Dispatched when...]

Output: The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.


Input: [Event name] canplaythrough [Dispatched when...]

Output: The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.


Input: [Event name] seeking [Dispatched when...]

Output: The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.


Input: [Event name] seeked [Dispatched when...]

Output: The seeking IDL attribute changed to false.


Input: [Event name] timeupdate [Dispatched when...]

Output: The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.


Input: [Event name] ended [Dispatched when...]

Output: Playback has stopped because the end of the media resource was reached.


Input: [Event name] ratechange [Dispatched when...]

Output: Either the defaultPlaybackRate or the playbackRate attribute has just been updated.


Input: [Event name] durationchange [Dispatched when...]

Output: The duration attribute has just been updated.


Input: [Event name] volumechange [Dispatched when...]

Output: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.


Input: [Common Field Names] name [Definitions] This property is set to the ECMAScript string value of the event name. [Optional]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connectionid [Definitions] This property is the ECMAScript string value of the ID of the Connection object associated with this event. [Optional]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] protocol [Definitions] This property is an ECMAScript string which identifies the protocol used by the event source; although this property is OPTIONAL, it is recommended that platforms provide it in order to allow applications to tailor their behavior (see Appendix E for a suggested set of protocol identifiers) [Optional]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] info [Definitions] This property provides a reference to an object which MAY contain platform or protocol dependent information specific to the event. [Optional]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] reason [Definitions] This property, although not provided by every event, when present provides a code indicating the status of the operation which triggered this event, or a reason for the occurrence of this event. [Optional]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connection [Definitions] An ECMAScript object reference to the Connection object identified by the connectionid property for this event. [Optional]

Output: false

Voice Browser Call Control: CCXML Version 1.0


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

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Name] next [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] must evaluate to a valid URI [Description]

Output: An ECMAScript expression which returns the URI of the resource to be fetched.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] In processed mode "application/ccxml+xml". In raw mode "*/*". [Valid Values] MIME Types formatted as per HTTP Accept header [RFC2616] [Description]

Output: An ECMAScript expression which returns a character string setting the value of the HTTP Accept header to tell the application server what content type the application wishes to have returned.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it must be submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used to fetch the URI post This indicates that the "POST" method must be used while submitting the URI to the web server.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] fetchid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive 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 identifier can be acquired from the fetch completion event. Every fetch request must receive a unique fetch identifier, even if the request is for the same URI

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] timeout [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

Output: The character string returned must be interpreted as a time interval. This interval begins when the fetch is executed. The fetch must fail if not completed at the end of this interval. A failed fetch must return the error.fetch event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age must be no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616] ). The document is not willing to use stale content, unless maxstale is also provided.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616] ). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" , otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mode [Required] false [Type] ECMAScript Expression [Default Value] processed [Valid Values] processed, raw [Description]

Output: Controls what the CCXML platform should do with fetched content. If set to processed (the default) the CCXML platform MUST attempt to parse and validate the returned content. If set to raw the platform MUST NOT attempt to process the data and MUST leave processing of the content to the application who can do what it wishes with the content via the content attribute of the fetch.done event

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dest [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A Valid URI [Description]

Output: An ECMAScript expression which returns a string that is the target of the outbound telephone call. A platform MUST support a telephone URI, as described in [RFC2806] [RFC3966] and MAY support other URI schemes such as "sip:" or "h323:" or a SIP URI as described in [RFC3261] .

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive the identifier of the Connection on which the outgoing call is attempted.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] aai [Required] false [Type] ECMAScript Expression [Default Value] none [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] callerid [Required] false [Type] ECMAScript Expression [Default Value] none [Description]

Output: An ECMAScript expression which returns a string defining the caller identity to be used when making the outbound connection. The format of this information is protocol and platform specific but might consist of a telephone URI, as described in [RFC2806] [RFC3966] or a SIP URI as described in [RFC3261] . Note: An implementation platform is not required to use the specified data and certain protocols and network elements may prevent its use. If the platform does not support the specification of callerid it must raise a connection.progressing event and indicate that the use of callerid is not supported.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform when establishing the outbound connection. This information may consist of protocol-specific parameters, protocol selection guidelines, or routing hints. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] timeout [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

Output: The character string returned is interpreted as a time interval. This interval begins when createcall is executed. The createcall must fail if not completed by the end of this interval. A completion is defined as the call getting to a CONNECTED state as signaled by a connection.connected event. A failed createcall must return the connection.failed event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] joinid [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] (valid connection, conference, or dialog ID) [Description]

Output: An ECMAScript expression that identifies a connection, conference, or dialog ID that the new call must be joined to. This is equivalent, from the perspective of the CCXML application, to performing a immediately following the . However, platforms may use knowledge about the connection/conference/dialog to which the new call will be connected to optimize the call creation process. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] joindirection [Required] false [Attribute Constraints] If this This attribute is specified only valid in conjunction with the joinid attribute MUST be present. attribute, otherwise ignored. [Type] ECMAScript Expression [Default Value] both [Valid Values] both calltransmit callreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the newly created connection, and the existing connection/conference/dialog referenced by joinid: both Specifes a full duplex connection where the media flows in both directions. calltransmit The new connection transmits media to the referenced connection/conference/dialog but does not receive any media streams. callreceive The new connection receives media from the referenced connection/conference/dialog but does not transmit any media streams.

Voice Browser Call Control: CCXML Version 1.0


Input: [Notation] {$ rule text $} [Interpretation]

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


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

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


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

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


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

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


Input: [Notation] $i$ [Interpretation]

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


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

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


Input: [Name] src [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a Dialog URL [Description]

Output: 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: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description]

Output: An 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. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of one or more whitespace separated CCXML variable names. These variables will be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value is first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute will receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of dialogstart, dialogterminate, join, or unjoin.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Attribute Constraints] Can not be used with conferenceid [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a connection. The specified connection will be associated with the dialog being prepared. If the attribute value is invalid, an error.semantic event will be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] conferenceid [Required] false [Attribute Constraints] Can not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of`a confe2ence bridge. A connection will be allocated for the dialog being prepared. If the attribute value is invalid, an error.semantic event will be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference specified by the connectionid or conferenceid attribute. The following values can be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent dialogstart is executed, but this attribute can be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment should make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 .

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned is interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned is interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist will be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method will be used by the dialog manager. post This indicates that the "POST" method will be used by the dialog manager.

Voice Browser Call Control: CCXML Version 1.0


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string


Input: [Keyword] text [State] Text [Control type] Text field [Data type]

Output: Text with no line breaks


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks