Input: [Description] When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application. [Source] webinos [Implications] Apps must have provenance data attached to them [Requirement]

Output: Trusted application source

System Applications WG: Security Model - W3C Wiki


Input: [Description] "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app" [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Requirement]

Output: App stores can revoke applications

System Applications WG: Security Model - W3C Wiki


Input: [Description] B2G: "App store must be able to set the default permissions for an app". [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] The user is not the only source of access control decisions. this also suggests a need for conflict resolution. [Requirement]

Output: External trusted party can set app default permissions

System Applications WG: Security Model - W3C Wiki


Input: [Description] Applications must be installed before executed [Source] B2G, webinos [Requirement]

Output: Installation

System Applications WG: Security Model - W3C Wiki


Input: [Description] The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example) [Source] B2G (user), webinos (user) [Implications] Access control settings must be changeable [Requirement]

Output: Owner override

System Applications WG: Security Model - W3C Wiki


Input: [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] There must be a standard way for applications to identify the permissions they have and lack [Requirement]

Output: App privilege visibility

System Applications WG: Security Model - W3C Wiki


Input: [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Requirement]

Output: Permission usability

System Applications WG: Security Model - W3C Wiki


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

Output: Immunity to browser-based threats

System Applications WG: Security Model - W3C Wiki


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

Output: Pre-installed app permissions

System Applications WG: Security Model - W3C Wiki


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

Output: Access to files outside owned by the platform

System Applications WG: Security Model - W3C Wiki


Input: [Expression] font name [Description] the name of the font [Setting]

Output: string


Input: [Expression] point size [Description] the size of the font [Setting]

Output: short int


Input: [Expression] weight [Description] use plain face [Setting]

Output: plain


Input: [Description] use bold face [Setting]

Output: bold


Input: [Expression] effects [Description] underline the text [Setting]

Output: underline


Input: [Expression] form [Description] use the italic form [Setting]

Output: italics


Input: [Term] dcterms:title [Purpose]

Output: The name of the dataset.

Describing Linked Datasets with the voiD Vocabulary

Using Dublin Core Metadata Terms in VoID for general dataset metadata


Input: [Term] dcterms:description [Purpose]

Output: A textual description of the dataset.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:creator [Purpose]

Output: An entity, such as a person, organisation, or service, that is primarily responsible for creating the dataset. The creator should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:publisher [Purpose]

Output: An entity, such as a person, organisation, or service, that is responsible for making the dataset available. The publisher should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:contributor [Purpose]

Output: An entity, such as a person, organisation, or service, that is responsible for making contributions to the dataset. The contributor should be described as an RDF resource, rather than just providing the name as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:source [Purpose]

Output: A related resource from which the dataset is derived. The source should be described as an RDF resource, rather than as a literal.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:date [Purpose]

Output: A point or period of time associated with an event in the life-cycle of the resource. The value should be formatted and data-typed as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:created [Purpose]

Output: Date of creation of the dataset. The value should be formatted and data-typed as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:issued [Purpose]

Output: Date of formal issuance (e.g., publication) of the dataset. The value should be formatted and datatyped as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Term] dcterms:modified [Purpose]

Output: Date on which the dataset was changed. The value should be formatted and datatyped as an xsd:date.

Describing Linked Datasets with the voiD Vocabulary


Input: [Event Name] dragstart [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] drag [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] dragenter [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Target]

Output: Immediate user selection or the body element


Input: [Event Name] dragleave [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] None [Target]

Output: Previous target element


Input: [Event Name] dragover [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Target]

Output: Current target element


Input: [Event Name] drop [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Current target element


Input: [Event Name] dragend [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Source node


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: [Property] additionalType [Description] An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. [Expected Type]

Output: URL


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

Output: Text


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

Output: URL


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

Output: Text


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

Output: URL


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

Output: Text


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

Output: Language


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

Output: Date


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

Output: Date


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

Output: Text


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

Output: Person or Organization


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

Output: Text


Input: [Property] reference [Description] The identifier of the reference, such as PMID, DOI, and PMCID. For example: . If the reference doesn't have ID, use URL. For example: . [Expected Type]

Output: Text or URL


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] The user agent begins looking for media data, as part of the resource selection algorithm. [Preconditions] networkState equals NETWORK_LOADING [Event name]

Output: loadstart


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] The user agent is fetching media data. [Preconditions] networkState equals NETWORK_LOADING [Event name]

Output: progress


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded. [Preconditions] networkState equals NETWORK_IDLE [Event name]

Output: suspend


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] The user agent finishes fetching the entire media resource. [Preconditions] networkState equals NETWORK_LOADED [Event name]

Output: load


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] The user agent stops fetching the media data before it is completely downloaded. [Preconditions] error is an object with the code MEDIA_ERR_ABORTED. networkState equals either NETWORK_EMPTY or NETWORK_LOADED, depending on when the download was aborted. [Event name]

Output: abort


Input: [Interface] ProgressEvent [PROGRESS] [Dispatched when...] An error occurs while fetching the media data. [Preconditions] error is an object with the code MEDIA_ERR_NETWORK or higher. networkState equals either NETWORK_EMPTY or NETWORK_LOADED, depending on when the download was aborted. [Event name]

Output: error


Input: [Interface] Event [Dispatched when...] 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, in which case it is fired synchronously during the load() method call). [Preconditions] networkState is NETWORK_EMPTY; all the DOM attributes are in their initial states. [Event name]

Output: emptied


Input: [Interface] ProgressEvent [Dispatched when...] The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. [Preconditions] networkState is NETWORK_LOADING. [Event name]

Output: stalled


Input: [Interface] Event [Dispatched when...] Playback has begun. Fired after the play() method has returned. [Preconditions] paused is newly false. [Event name]

Output: play


Input: [Interface] Event [Dispatched when...] Playback has been paused. Fired after the pause method has returned. [Preconditions] paused is newly true. [Event name]

Output: pause


Input: [Interface] Event [Dispatched when...] The user agent has just determined the duration and dimensions of the media resource. [Preconditions] readyState is newly equal to HAVE_METADATA or greater for the first time. [Event name]

Output: loadedmetadata


Input: [Interface] Event [Dispatched when...] The user agent can render the media data at the current playback position for the first time. [Preconditions] readyState newly increased to HAVE_CURRENT_DATA or greater for the first time. [Event name]

Output: loadeddata


Input: [Interface] Event [Dispatched when...] Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. [Preconditions] readyState is newly equal to or less than HAVE_CURRENT_DATA, and paused is false. Either seeking is true, or the current playback position is not contained in any of the ranges in buffered. It is possible for playback to stop for two other reasons without paused being false, but those two reasons do not fire this event: maybe playback ended, or playback stopped due to errors. [Event name]

Output: waiting


Input: [Interface] Event [Dispatched when...] Playback has started. [Preconditions] readyState is newly equal to or greater than HAVE_FUTURE_DATA, paused is false, seeking is false, or the current playback position is contained in one of the ranges in buffered. [Event name]

Output: playing


Input: [Interface] Event [Dispatched when...] 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. [Preconditions] readyState newly increased to HAVE_FUTURE_DATA or greater. [Event name]

Output: canplay


Input: [Interface] Event [Dispatched when...] 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. [Preconditions] readyState is newly equal to HAVE_ENOUGH_DATA. [Event name]

Output: canplaythrough


Input: [Interface] Event [Dispatched when...] The seeking DOM attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event. [Event name]

Output: seeking


Input: [Interface] Event [Dispatched when...] The seeking DOM attribute changed to false. [Event name]

Output: seeked


Input: [Interface] Event [Dispatched when...] The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously. [Event name]

Output: timeupdate


Input: [Interface] Event [Dispatched when...] Playback has stopped because the end of the media resource was reached. [Preconditions] currentTime equals the end of the media resource; ended is true. [Event name]

Output: ended


Input: [Interface] Event [Dispatched when...] Either the defaultPlaybackRate or the playbackRate attribute has just been updated. [Event name]

Output: ratechange


Input: [Interface] Event [Dispatched when...] The duration attribute has just been updated. [Event name]

Output: durationchange


Input: [Interface] Event [Dispatched when...] Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. [Event name]

Output: volumechange


Input: [Item] Illustrative example [Required?] suggested [Primary Audience] all [Notes]

Output: to illustrate the abstract


Input: [Item] Overview [Required?] optional [Primary Audience] all [Notes]

Output: A prose version of the TOC


Input: [Item] Introduction [Required?] optional [Primary Audience] all [Notes]

Output: Introduces key concepts and sets context for understanding the spec


Input: [Item] Background [Required?] optional [Primary Audience] ? [Notes]

Output: Gives Motivation/Historical Context for spec


Input: [Item] Use Cases and Requirements [Required?] required [Primary Audience] reviewers and Director of W3C [Notes]

Output: Explain what problems trying to solve. Explicitly required by W3C Director to progress specification to CR.


Input: [Item] Transition Criteria [Required?] some [Primary Audience] participants [Notes]

Output: CR exit criteria. Suggest expanding to all other specs to explain exit criteria of other stages. N/A to REC / NOTE


Input: [Item] Abstract / 2-sentence summary [Required?] all [Primary Audience]

Output: We recommend compressing the abstract into a 2-sentence summary suitable for search results and other listings


Input: [Item] Illustrative example [Required?] suggested [Notes] to illustrate the abstract [Primary Audience]

Output: all


Input: [Item] TOC [Required?] all [Primary Audience]

Output: all


Input: [Item] Overview [Required?] optional [Notes] A prose version of the TOC [Primary Audience]

Output: all


Input: [Item] Introduction [Required?] optional [Notes] Introduces key concepts and sets context for understanding the spec [Primary Audience]

Output: all


Input: [Item] Background [Required?] optional [Notes] Gives Motivation/Historical Context for spec [Primary Audience]


Input: [Item] Use Cases and Requirements [Required?] required [Notes] Explain what problems trying to solve. Explicitly required by W3C Director to progress specification to CR. [Primary Audience]

Output: reviewers and Director of W3C


Input: [Item] Scope [Required?] optional [Primary Audience]

Output: editors/WG


Input: [Item] Transition Criteria [Required?] some [Notes] CR exit criteria. Suggest expanding to all other specs to explain exit criteria of other stages. N/A to REC / NOTE [Primary Audience]

Output: participants


Input: [Item] References [Required?] all [Primary Audience]

Output: implementers


Input: [Item] Conformance [Required?] some [Primary Audience]

Output: implementers


Input: [Item] Index/Glossary [Required?] optional [Primary Audience]

Output: all


Input: [Item] Acknowledgements [Required?] all [Primary Audience]

Output: acknowledged


Input: [Keyword] hidden [State] Hidden [Data type] An arbitrary string [Control type]


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

Output: Text field


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

Output: Search field


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

Output: A text field


Input: [Keyword] url [State] URL [Data type] An absolute IRI [Control type]

Output: A text field


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

Output: A text field


Input: [Keyword] password [State] Password [Data type] Text with no line breaks (sensitive information) [Control type]

Output: Text field that obscures data entry


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

Output: A date and time control


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

Output: A date control


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

Output: A month control


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

Output: A week control


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

Output: A time control


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

Output: A date and time control


Input: [Keyword] number [State] Number [Data type] A numerical value [Control type]

Output: A text field or spinner control


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

Output: A slider control or similar


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

Output: A color well


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

Output: A checkbox


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

Output: A radio button


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

Output: A label and a button


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

Output: A button


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

Output: Either a clickable image, or a button


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

Output: A button


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

Output: A button


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Description] 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. [Valid Values]

Output: A valid target URL

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Description] 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.. [Valid Values]

Output: ccxml dialog

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] 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. [Valid Values]

Output: ECMAScript Variable

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Description] 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. [Valid Values]

Output: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

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 [Description] 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. [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Description] 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. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: no

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


Input: [Additive?] yes ['set'] no ['animate Color'] no ['animate Transform'] yes [Notes] Additive means that a transformation is post-multiplied to the base set of transformations. ['animate']

Output: no

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


Input: [Item] Abstract / 2-sentence summary [Primary Audience] We recommend compressing the abstract into a 2-sentence summary suitable for search results and other listings [Required?]

Output: all


Input: [Item] Illustrative example [Primary Audience] all [Notes] to illustrate the abstract [Required?]

Output: suggested


Input: [Item] TOC [Primary Audience] all [Required?]

Output: all


Input: [Item] Overview [Primary Audience] all [Notes] A prose version of the TOC [Required?]

Output: optional


Input: [Item] Introduction [Primary Audience] all [Notes] Introduces key concepts and sets context for understanding the spec [Required?]

Output: optional


Input: [Item] Background [Primary Audience] ? [Notes] Gives Motivation/Historical Context for spec [Required?]

Output: optional


Input: [Item] Use Cases and Requirements [Primary Audience] reviewers and Director of W3C [Notes] Explain what problems trying to solve. Explicitly required by W3C Director to progress specification to CR. [Required?]

Output: required


Input: [Item] Scope [Primary Audience] editors/WG [Required?]

Output: optional


Input: [Item] Transition Criteria [Primary Audience] participants [Notes] CR exit criteria. Suggest expanding to all other specs to explain exit criteria of other stages. N/A to REC / NOTE [Required?]

Output: some


Input: [Item] References [Primary Audience] implementers [Required?]

Output: all


Input: [Item] Conformance [Primary Audience] implementers [Required?]

Output: some


Input: [Item] Index/Glossary [Primary Audience] all [Required?]

Output: optional


Input: [Item] Acknowledgements [Primary Audience] acknowledged [Required?]

Output: all


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

Output: a Dialog URL

Voice Browser Call Control: CCXML Version 1.0


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

Output: a Valid MIME Type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [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". [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [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. [Valid Values]

Output: ECMAScript Variable

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 [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. [Valid Values]

Output: Connection IDs

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 [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. [Valid Values]

Output: Conference IDs

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [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 . [Valid Values]

Output: both dialogtransmit dialogreceive

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [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. [Valid Values]

Output: An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616]

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [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. [Valid Values]

Output: An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616]

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 [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. [Valid Values]

Output: valid media encoding type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [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. [Valid Values]

Output: get post

Voice Browser Call Control: CCXML Version 1.0


Input: [Module] Measuring [Type] class [Definition] A sensing device is a device that implements sensing. [Term Name]

Output: SensingDevice


Input: [Module] Measuring [Type] class [Definition] A data sheet records properties of a sensor. A data sheet might describe for example the accuracy in various conditions, the power use, the types of connectors that the sensor has, etc. Generally a sensor's properties are recorded directly (with hasMeasurementCapability, for example), but the data sheet can be used for example to record the manufacturers specifications verses observed capabilites, or if more is known than the manufacturer specifies, etc. The data sheet is an information object about the sensor's properties, rather than a direct link to the actual properties themselves. [Term Name]

Output: SensorDataSheet


Input: [Module] Measuring [Type] property [Definition] Relation between a Sensor and a Property that the sensor can observe. Note that, given the DUL modelling of Qualities, a sensor defined with 'observes only Windspeed' technically links the sensor to particular instances of Windspeed, not to the concept itself - OWL can't express concept-concept relations, only individual-individual. The property composition ensures that if an observation is made of a particular quality then one can infer that the sensor observes that quality. [Term Name]

Output: observes


Input: [Module] MeasuringCapability [Type] class [Definition] The closeness of agreement between the value of an observation and the true value of the observed quality. [Term Name]

Output: Accuracy


Input: [Module] MeasuringCapability [Type] class [Definition] An observed value for which the probability of falsely claiming the absence of a component in a material is ÃŽÂ², given a probability ÃŽÂ± of falsely claiming its presence. [Term Name]

Output: DetectionLimit


Input: [Module] MeasuringCapability [Type] class [Definition] A, continuous or incremental, change in the reported values of observations over time for an unchanging quality. [Term Name]

Output: Drift


Input: [Module] MeasuringCapability [Type] class [Definition] The smallest possible time between one observation and the next. [Term Name]

Output: Frequency


Input: [Module] MeasuringCapability [Type] class [Definition] The time between a request for an observation and the sensor providing a result. [Term Name]

Output: Latency


Input: [Module] MeasuringCapability [Type] class [Definition] Collects together measurement properties (accuracy, range, precision, etc) and the environmental conditions in which those properties hold, representing a specification of a sensor's capability in those conditions. The conditions specified here are those that affect the measurement properties, while those in OperatingRange represent the sensor's standard operating conditions, including conditions that don't affect the observations. [Term Name]

Output: MeasurementCapability


Input: [Module] MeasuringCapability [Type] class [Definition] An identifiable and observable characteristic of a sensor's observations or ability to make observations. [Term Name]

Output: MeasurementProperty


Input: [Module] MeasuringCapability [Type] class [Definition] The set of values that the sensor can return as the result of an observation under the defined conditions with the defined measurement properties. (If no conditions are specified or the conditions do not specify a range for the observed qualities, the measurement range is to be taken as the condition for the observed qualities.) [Term Name]

Output: MeasurementRange


Input: [Module] MeasuringCapability [Type] class [Definition] The closeness of agreement between replicate observations on an unchanged or similar quality value: i.e., a measure of a sensor's ability to consitently reproduce an observation. [Term Name]

Output: Precision


Input: [Module] MeasuringCapability [Type] class [Definition] The smallest difference in the value of a quality being observed that would result in perceptably different values of observation results. [Term Name]

Output: Resolution


Input: [Module] MeasuringCapability [Type] class [Definition] The time between a (step) change inthe value of an observed quality and a sensor (possibly with specified error) 'settling' on an observed value. [Term Name]

Output: ResponseTime


Input: [Module] MeasuringCapability [Type] class [Definition] Selectivity is a property of a sensor whereby it provides observed values for one or more qualities such that the values of each quality are independent of other qualities in the phenomenon, body, or substance being investigated. [Term Name]

Output: Selectivity


Input: [Module] MeasuringCapability [Type] class [Definition] Sensitivity is the quotient of the change in a result of sensor and the corresponding change in a value of a quality being observed. [Term Name]

Output: Sensitivity


Input: [Module] MeasuringCapability [Type] property [Definition] Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor. [Term Name]

Output: hasMeasurementCapability


Input: [Module] MeasuringCapability [Type] property [Definition] Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability). [Term Name]

Output: hasMeasurementProperty


Input: [Dispatched when...] The user agent begins looking for media data, as part of the resource selection algorithm. [Event name]

Output: loadstart


Input: [Dispatched when...] The user agent is fetching media data. [Event name]

Output: progress


Input: [Dispatched when...] The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded. [Event name]

Output: suspend


Input: [Dispatched when...] The user agent stops fetching the media data before it is completely downloaded, but not due to an error. [Event name]

Output: abort


Input: [Dispatched when...] An error occurs while fetching the media data. [Event name]

Output: error


Input: [Dispatched when...] 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). [Event name]

Output: emptied


Input: [Dispatched when...] The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. [Event name]

Output: stalled


Input: [Dispatched when...] Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin. [Event name]

Output: play


Input: [Dispatched when...] Playback has been paused. Fired after the pause() method has returned. [Event name]

Output: pause


Input: [Dispatched when...] The user agent has just determined the duration and dimensions of the media resource [Event name]

Output: loadedmetadata


Input: [Dispatched when...] The user agent can render the media data at the current playback position for the first time. [Event name]

Output: loadeddata


Input: [Dispatched when...] Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. [Event name]

Output: waiting


Input: [Dispatched when...] Playback has started. [Event name]

Output: playing


Input: [Dispatched when...] 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. [Event name]

Output: canplay


Input: [Dispatched when...] 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. [Event name]

Output: canplaythrough


Input: [Dispatched when...] 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. [Event name]

Output: seeking


Input: [Dispatched when...] The seeking IDL attribute changed to false. [Event name]

Output: seeked


Input: [Dispatched when...] The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously. [Event name]

Output: timeupdate


Input: [Dispatched when...] Playback has stopped because the end of the media resource was reached. [Event name]

Output: ended


Input: [Dispatched when...] Either the defaultPlaybackRate or the playbackRate attribute has just been updated. [Event name]

Output: ratechange


Input: [Dispatched when...] The duration attribute has just been updated. [Event name]

Output: durationchange


Input: [Dispatched when...] Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. [Event name]

Output: volumechange


Input: [Module] Deployment [Term Name] Deployment [Type] class [Definition]

Output: The ongoing Process of Entities (for the purposes of this ontology, mainly sensors) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal.


Input: [Module] Deployment [Term Name] DeploymentRelatedProcess [Type] class [Definition]

Output: Place to group all the various Processes related to Deployment. For example, as well as Deplyment, installation, maintenance, deployment of further sensors and the like would all be classified under DeploymentRelatedProcess.


Input: [Module] Deployment [Term Name] deployedOnPlatform [Type] property [Definition]

Output: Relation between a deployment and the platform on which the system was deployed.


Input: [Module] Deployment [Term Name] deployedSystem [Type] property [Definition]

Output: Relation between a deployment and the deployed system.


Input: [Module] Deployment [Term Name] deploymentProcessPart [Type] property [Definition]

Output: Has part relation between a deployment process and its constituent processes.


Input: [Module] Deployment [Term Name] hasDeployment [Type] property [Definition]

Output: Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment.


Input: [Module] Deployment [Term Name] inDeployment [Type] property [Definition]

Output: Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment.


Input: [Module] PlatformSite [Term Name] Platform [Type] class [Definition]

Output: An Entity to which other Entities can be attached - particuarly Sensors and other Platforms. For example, a post might act as the Platform, a bouy might act as a Platform, or a fish might act as a Platform for an attached sensor.


Input: [Module] PlatformSite [Term Name] attachedSystem [Type] property [Definition]

Output: Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform.


Input: [Module] PlatformSite [Term Name] onPlatform [Type] property [Definition]

Output: Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion).


Input: [Module] OperatingRestriction [Term Name] MaintenanceSchedule [Type] class [Definition]

Output: Schedule of maintenance for a system/sensor in the specified conditions.


Input: [Module] OperatingRestriction [Term Name] OperatingProperty [Type] class [Definition]

Output: An identifiable characteristic of the environmental and other conditions in which the sensor is intended to operate. May include power ranges, power sources, standard configurations, attachments and the like.


Input: [Module] OperatingRestriction [Term Name] OperatingRange [Type] class [Definition]

Output: The environmental conditions and characteristics of a system/sensor's normal operating environment. Can be used to specify for example the standard environmental conditions in which the sensor is expected to operate (a Condition with no OperatingProperty), or how the environmental and other operating properties relate: i.e., that the maintenance schedule or power requirements differ according to the conditions.


Input: [Module] OperatingRestriction [Term Name] SurvivalProperty [Type] class [Definition]

Output: An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted.


Input: [Module] OperatingRestriction [Term Name] SurvivalRange [Type] class [Definition]

Output: The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold.


Input: [Module] OperatingRestriction [Term Name] SystemLifetime [Type] class [Definition]

Output: Total useful life of a sensor/system (expressed as total life since manufacture, time in use, number of operations, etc.).


Input: [Module] OperatingRestriction [Term Name] hasOperatingProperty [Type] property [Definition]

Output: Relation from an OperatingRange to a Property. For example, to a battery lifetime.


Input: [Module] OperatingRestriction [Term Name] hasOperatingRange [Type] property [Definition]

Output: Relation from a System to an OperatingRange describing the normal operating environment of the System.


Input: [Module] OperatingRestriction [Term Name] hasSurvivalProperty [Type] property [Definition]

Output: Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged.


Input: [Module] OperatingRestriction [Term Name] hasSurvivalRange [Type] property [Definition]

Output: A Relation from a System to a SurvivalRange.


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: no

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


Input: [Additive?] yes ['animate'] no ['animate Color'] no ['animate Transform'] yes [Notes] Additive means that a transformation is post-multiplied to the base set of transformations. ['set']

Output: no

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


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

Output: yes

Animation - W3C SVG 1.0 Specification - Candidate Recommendation 20001102


Input: [Term Name] Deployment [Type] class [Definition] The ongoing Process of Entities (for the purposes of this ontology, mainly sensors) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal. [Module]

Output: Deployment


Input: [Term Name] DeploymentRelatedProcess [Type] class [Definition] Place to group all the various Processes related to Deployment. For example, as well as Deplyment, installation, maintenance, deployment of further sensors and the like would all be classified under DeploymentRelatedProcess. [Module]

Output: Deployment


Input: [Term Name] deployedOnPlatform [Type] property [Definition] Relation between a deployment and the platform on which the system was deployed. [Module]

Output: Deployment


Input: [Term Name] deployedSystem [Type] property [Definition] Relation between a deployment and the deployed system. [Module]

Output: Deployment


Input: [Term Name] deploymentProcessPart [Type] property [Definition] Has part relation between a deployment process and its constituent processes. [Module]

Output: Deployment


Input: [Term Name] hasDeployment [Type] property [Definition] Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment. [Module]

Output: Deployment


Input: [Term Name] inDeployment [Type] property [Definition] Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment. [Module]

Output: Deployment


Input: [Term Name] Platform [Type] class [Definition] An Entity to which other Entities can be attached - particuarly Sensors and other Platforms. For example, a post might act as the Platform, a bouy might act as a Platform, or a fish might act as a Platform for an attached sensor. [Module]

Output: PlatformSite


Input: [Term Name] attachedSystem [Type] property [Definition] Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform. [Module]

Output: PlatformSite


Input: [Term Name] onPlatform [Type] property [Definition] Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion). [Module]

Output: PlatformSite


Input: [Term Name] MaintenanceSchedule [Type] class [Definition] Schedule of maintenance for a system/sensor in the specified conditions. [Module]

Output: OperatingRestriction


Input: [Term Name] OperatingProperty [Type] class [Definition] An identifiable characteristic of the environmental and other conditions in which the sensor is intended to operate. May include power ranges, power sources, standard configurations, attachments and the like. [Module]

Output: OperatingRestriction


Input: [Term Name] OperatingRange [Type] class [Definition] The environmental conditions and characteristics of a system/sensor's normal operating environment. Can be used to specify for example the standard environmental conditions in which the sensor is expected to operate (a Condition with no OperatingProperty), or how the environmental and other operating properties relate: i.e., that the maintenance schedule or power requirements differ according to the conditions. [Module]

Output: OperatingRestriction


Input: [Term Name] SurvivalProperty [Type] class [Definition] An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted. [Module]

Output: OperatingRestriction


Input: [Term Name] SurvivalRange [Type] class [Definition] The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold. [Module]

Output: OperatingRestriction


Input: [Term Name] SystemLifetime [Type] class [Definition] Total useful life of a sensor/system (expressed as total life since manufacture, time in use, number of operations, etc.). [Module]

Output: OperatingRestriction


Input: [Term Name] hasOperatingProperty [Type] property [Definition] Relation from an OperatingRange to a Property. For example, to a battery lifetime. [Module]

Output: OperatingRestriction


Input: [Term Name] hasOperatingRange [Type] property [Definition] Relation from a System to an OperatingRange describing the normal operating environment of the System. [Module]

Output: OperatingRestriction


Input: [Term Name] hasSurvivalProperty [Type] property [Definition] Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged. [Module]

Output: OperatingRestriction


Input: [Term Name] hasSurvivalRange [Type] property [Definition] A Relation from a System to a SurvivalRange. [Module]

Output: OperatingRestriction


Input: [Module] Deployment [Term Name] Deployment [Definition] The ongoing Process of Entities (for the purposes of this ontology, mainly sensors) deployed for a particular purpose. For example, a particular Sensor deployed on a Platform, or a whole network of Sensors deployed for an observation campaign. The deployment may have sub processes, such as installation, maintenance, addition, and decomissioning and removal. [Type]

Output: class


Input: [Module] Deployment [Term Name] DeploymentRelatedProcess [Definition] Place to group all the various Processes related to Deployment. For example, as well as Deplyment, installation, maintenance, deployment of further sensors and the like would all be classified under DeploymentRelatedProcess. [Type]

Output: class


Input: [Module] Deployment [Term Name] deployedOnPlatform [Definition] Relation between a deployment and the platform on which the system was deployed. [Type]

Output: property


Input: [Module] Deployment [Term Name] deployedSystem [Definition] Relation between a deployment and the deployed system. [Type]

Output: property


Input: [Module] Deployment [Term Name] deploymentProcessPart [Definition] Has part relation between a deployment process and its constituent processes. [Type]

Output: property


Input: [Module] Deployment [Term Name] hasDeployment [Definition] Relation between a System and a Deployment, recording that the System/Sensor was deployed in that Deployment. [Type]

Output: property


Input: [Module] Deployment [Term Name] inDeployment [Definition] Relation between a Platform and a Deployment, recording that the object was used as a platform for a system/sensor for a particular deployment: as in this PhysicalObject is acting as a Platform inDeployment Deployment. [Type]

Output: property


Input: [Module] PlatformSite [Term Name] Platform [Definition] An Entity to which other Entities can be attached - particuarly Sensors and other Platforms. For example, a post might act as the Platform, a bouy might act as a Platform, or a fish might act as a Platform for an attached sensor. [Type]

Output: class


Input: [Module] PlatformSite [Term Name] attachedSystem [Definition] Relation between a Platform and any Systems (e.g., Sensors) that are attached to the Platform. [Type]

Output: property


Input: [Module] PlatformSite [Term Name] onPlatform [Definition] Relation between a System (e.g., a Sensor) and a Platform. The relation locates the sensor relative to other described entities entities: i.e., the Sensor s1's location is Platform p1. More precise locations for sensors in space (relative to other entities, where attached to another entity, or in 3D space) are made using DOLCE's Regions (SpaceRegion). [Type]

Output: property


Input: [Module] OperatingRestriction [Term Name] MaintenanceSchedule [Definition] Schedule of maintenance for a system/sensor in the specified conditions. [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] OperatingProperty [Definition] An identifiable characteristic of the environmental and other conditions in which the sensor is intended to operate. May include power ranges, power sources, standard configurations, attachments and the like. [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] OperatingRange [Definition] The environmental conditions and characteristics of a system/sensor's normal operating environment. Can be used to specify for example the standard environmental conditions in which the sensor is expected to operate (a Condition with no OperatingProperty), or how the environmental and other operating properties relate: i.e., that the maintenance schedule or power requirements differ according to the conditions. [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] SurvivalProperty [Definition] An identifiable characteristic that represents the extent of the sensors useful life. Might include for example total battery life or number of recharges, or, for sensors that are used only a fixed number of times, the number of observations that can be made before the sensing capability is depleted. [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] SurvivalRange [Definition] The conditions a sensor can be exposed to without damage: i.e., the sensor continues to operate as defined using MeasurementCapability. If, however, the SurvivalRange is exceeded, the sensor is 'damaged' and MeasurementCapability specifications may no longer hold. [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] SystemLifetime [Definition] Total useful life of a sensor/system (expressed as total life since manufacture, time in use, number of operations, etc.). [Type]

Output: class


Input: [Module] OperatingRestriction [Term Name] hasOperatingProperty [Definition] Relation from an OperatingRange to a Property. For example, to a battery lifetime. [Type]

Output: property


Input: [Module] OperatingRestriction [Term Name] hasOperatingRange [Definition] Relation from a System to an OperatingRange describing the normal operating environment of the System. [Type]

Output: property


Input: [Module] OperatingRestriction [Term Name] hasSurvivalProperty [Definition] Relation from a SurvivalRange to a Property describing the survial range of a system. For example, to the temperature extreme that a system can withstand before being considered damaged. [Type]

Output: property


Input: [Module] OperatingRestriction [Term Name] hasSurvivalRange [Definition] A Relation from a System to a SurvivalRange. [Type]

Output: property


Input: [Module] Measuring [Term Name] SensingDevice [Type] class [Definition]

Output: A sensing device is a device that implements sensing.


Input: [Module] Measuring [Term Name] SensorDataSheet [Type] class [Definition]

Output: A data sheet records properties of a sensor. A data sheet might describe for example the accuracy in various conditions, the power use, the types of connectors that the sensor has, etc. Generally a sensor's properties are recorded directly (with hasMeasurementCapability, for example), but the data sheet can be used for example to record the manufacturers specifications verses observed capabilites, or if more is known than the manufacturer specifies, etc. The data sheet is an information object about the sensor's properties, rather than a direct link to the actual properties themselves.


Input: [Module] Measuring [Term Name] observes [Type] property [Definition]

Output: Relation between a Sensor and a Property that the sensor can observe. Note that, given the DUL modelling of Qualities, a sensor defined with 'observes only Windspeed' technically links the sensor to particular instances of Windspeed, not to the concept itself - OWL can't express concept-concept relations, only individual-individual. The property composition ensures that if an observation is made of a particular quality then one can infer that the sensor observes that quality.


Input: [Module] MeasuringCapability [Term Name] Accuracy [Type] class [Definition]

Output: The closeness of agreement between the value of an observation and the true value of the observed quality.


Input: [Module] MeasuringCapability [Term Name] DetectionLimit [Type] class [Definition]

Output: An observed value for which the probability of falsely claiming the absence of a component in a material is ÃŽÂ², given a probability ÃŽÂ± of falsely claiming its presence.


Input: [Module] MeasuringCapability [Term Name] Drift [Type] class [Definition]

Output: A, continuous or incremental, change in the reported values of observations over time for an unchanging quality.


Input: [Module] MeasuringCapability [Term Name] Frequency [Type] class [Definition]

Output: The smallest possible time between one observation and the next.


Input: [Module] MeasuringCapability [Term Name] Latency [Type] class [Definition]

Output: The time between a request for an observation and the sensor providing a result.


Input: [Module] MeasuringCapability [Term Name] MeasurementCapability [Type] class [Definition]

Output: Collects together measurement properties (accuracy, range, precision, etc) and the environmental conditions in which those properties hold, representing a specification of a sensor's capability in those conditions. The conditions specified here are those that affect the measurement properties, while those in OperatingRange represent the sensor's standard operating conditions, including conditions that don't affect the observations.


Input: [Module] MeasuringCapability [Term Name] MeasurementProperty [Type] class [Definition]

Output: An identifiable and observable characteristic of a sensor's observations or ability to make observations.


Input: [Module] MeasuringCapability [Term Name] MeasurementRange [Type] class [Definition]

Output: The set of values that the sensor can return as the result of an observation under the defined conditions with the defined measurement properties. (If no conditions are specified or the conditions do not specify a range for the observed qualities, the measurement range is to be taken as the condition for the observed qualities.)


Input: [Module] MeasuringCapability [Term Name] Precision [Type] class [Definition]

Output: The closeness of agreement between replicate observations on an unchanged or similar quality value: i.e., a measure of a sensor's ability to consitently reproduce an observation.


Input: [Module] MeasuringCapability [Term Name] Resolution [Type] class [Definition]

Output: The smallest difference in the value of a quality being observed that would result in perceptably different values of observation results.


Input: [Module] MeasuringCapability [Term Name] ResponseTime [Type] class [Definition]

Output: The time between a (step) change inthe value of an observed quality and a sensor (possibly with specified error) 'settling' on an observed value.


Input: [Module] MeasuringCapability [Term Name] Selectivity [Type] class [Definition]

Output: Selectivity is a property of a sensor whereby it provides observed values for one or more qualities such that the values of each quality are independent of other qualities in the phenomenon, body, or substance being investigated.


Input: [Module] MeasuringCapability [Term Name] Sensitivity [Type] class [Definition]

Output: Sensitivity is the quotient of the change in a result of sensor and the corresponding change in a value of a quality being observed.


Input: [Module] MeasuringCapability [Term Name] hasMeasurementCapability [Type] property [Definition]

Output: Relation from a Sensor to a MeasurementCapability describing the measurement properties of the sensor.


Input: [Module] MeasuringCapability [Term Name] hasMeasurementProperty [Type] property [Definition]

Output: Relation from a MeasurementCapability to a MeasurementProperty. For example, to an accuracy (see notes at MeasurementCapability).


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

Output: Probably a layout table


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

Output: Probably a layout table


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

Output: Probably a layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

Output: Not a good indicator (both layout and non-layout tables have historically been given this attribute)


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

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


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

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [id] i1 [target] RFC2616 [type] design [draft] 01 [title]

Output: HTTP Version should be case sensitive


Input: [id] i3 [target] RFC2616 [type] design [draft] 01 [title]

Output: Chunk Size Definition


Input: [id] i5 [target] RFC2616 [type] design [draft] 01 [title]

Output: Via is a MUST


Input: [id] i6 [target] RFC2616 [type] design [draft] 01 [title]

Output: Fragments allowed in Location


Input: [id] i10 [target] RFC2616 [type] design [draft] 01 [title]

Output: Safe Methods vs Redirection


Input: [id] i11 [target] RFC2616 [type] design [draft] 01 [title]

Output: URI includes query


Input: [id] i12 [target] RFC2616 [type] design [draft] 01 [title]

Output: Invalidation after Update or Delete


Input: [id] i14 [target] RFC2616 [type] design [draft] 01 [title]

Output: Clarification regarding quoting of charset values


Input: [id] i15 [target] RFC2616 [type] design [draft] 01 [title]

Output: No close on 1xx responses


Input: [id] i17 [target] RFC2616 [type] design [draft] 01 [title]

Output: Revise description of the POST method


Input: [id] i18 [target] RFC2616 [type] design [draft] 01 [title]

Output: Cache validators in 206 responses


Input: [id] i25 [target] RFC2616 [type] design [draft] 04 [title]

Output: Accept-Encoding BNF


Input: [id] i31 [target] RFC2616 [type] design [draft] 04 [title]

Output: qdtext BNF


Input: [id] i62 [target] RFC2616 [type] design [title]

Output: Whitespace in quoted-pair


Input: [id] i2 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: 'unsafe' characters


Input: [id] i4 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Message Length


Input: [id] i7 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Editors Notes


Input: [id] i8 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Media type registrations


Input: [id] i9 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Trailer


Input: [id] i16 [target] RFC2616 [type] editorial [draft] 01 [title]

Output: Remove 'identity' token references


Input: [id] i26 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Import query BNF


Input: [id] i42 [target] RFC2616 [type] editorial [draft] 02 [title]

Output: RFC2606 compliance


Input: [id] i44 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Unneeded references


Input: [id] i45 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: RFC977 reference


Input: [id] i46 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: references to RFC1700


Input: [id] i47 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: inconsistency in date format explanation


Input: [id] i48 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: Date reference typo


Input: [id] i49 [target] RFC2616 [type] editorial [draft] 03 [title]

Output: Connection header text


Input: [id] i65 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Informative references


Input: [id] i66 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: ISO-8859-1 Reference


Input: [id] i68 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Encoding References Normative


Input: [id] i84 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Redundant cross-references


Input: [id] i86 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: Normative up-to-date references


Input: [id] i87 [target] RFC2616 [type] editorial [draft] 04 [title]

Output: typo in 13.2.2


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Description] 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 must send the event to. [Valid Values]

Output: A valid target URI

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Description] An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event must be dispatched to. [Valid Values]

Output: ccxml dialog basichttp

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [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 event being sent. [Valid Values]

Output: ECMAScript Variable

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Description] The character string returned must be interpreted as a time interval. The send element must return immediately, but the event must not be 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 delayed event queue for sending events must be maintained locally. Any events waiting to be sent must be purged when the session that issued this request terminates. [Valid Values]

Output: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with inline content [Type] Var List [Default Value] none [Description] A list of zero or more whitespace separated CCXML variable names to be included with the event. Values for these variables are evaluated when the element is processed See section 9.2.3.1 for details on how these variables are made available to the target. [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The ECMAScript object returned contains information which may be used by the implementing platform to configure the Event I/O Processor. The meaning of these hints is specific to the implementing platform and the Event I/O Processor. 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. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid target URI [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 must 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 basichttp [Description]

Output: An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event must be dispatched to.

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 must receive an internally generated unique string identifier to be associated with the event being sent.

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 must be interpreted as a time interval. The send element must return immediately, but the event must not be 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 delayed event queue for sending events must be maintained locally. Any events waiting to be sent must be purged when the session that issued this request terminates.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] name [Required] false [Attribute Constraints] This attribute must 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 event name being generated. The event name may include alphanumeric characters characters, "_" (underscore) and the "." (dot) character. The first character MUST NOT be a dot or a digit. event names are case-insensitive.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must 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. Values for these variables are evaluated when the element is processed See section 9.2.3.1 for details on how these variables are made available to the target.

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 I/O Processor. The meaning of these hints is specific to the implementing platform and the Event I/O Processor. 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: [id] i1 [title] HTTP Version should be case sensitive [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i3 [title] Chunk Size Definition [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i5 [title] Via is a MUST [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i6 [title] Fragments allowed in Location [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i10 [title] Safe Methods vs Redirection [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i11 [title] URI includes query [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i12 [title] Invalidation after Update or Delete [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i14 [title] Clarification regarding quoting of charset values [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i15 [title] No close on 1xx responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i17 [title] Revise description of the POST method [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i18 [title] Cache validators in 206 responses [target] RFC2616 [draft] 01 [type]

Output: design


Input: [id] i25 [title] Accept-Encoding BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i31 [title] qdtext BNF [target] RFC2616 [draft] 04 [type]

Output: design


Input: [id] i62 [title] Whitespace in quoted-pair [target] RFC2616 [type]

Output: design


Input: [id] i2 [title] 'unsafe' characters [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i4 [title] Message Length [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i7 [title] Editors Notes [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i8 [title] Media type registrations [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i9 [title] Trailer [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i16 [title] Remove 'identity' token references [target] RFC2616 [draft] 01 [type]

Output: editorial


Input: [id] i26 [title] Import query BNF [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i42 [title] RFC2606 compliance [target] RFC2616 [draft] 02 [type]

Output: editorial


Input: [id] i44 [title] Unneeded references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i45 [title] RFC977 reference [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i46 [title] references to RFC1700 [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i47 [title] inconsistency in date format explanation [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i48 [title] Date reference typo [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i49 [title] Connection header text [target] RFC2616 [draft] 03 [type]

Output: editorial


Input: [id] i65 [title] Informative references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i66 [title] ISO-8859-1 Reference [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i68 [title] Encoding References Normative [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i84 [title] Redundant cross-references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i86 [title] Normative up-to-date references [target] RFC2616 [draft] 04 [type]

Output: editorial


Input: [id] i87 [title] typo in 13.2.2 [target] RFC2616 [draft] 04 [type]

Output: editorial


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

Output: a Dialog URI

Voice Browser Call Control: CCXML Version 1.0


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

Output: a Valid MIME Type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [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". [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] parameters [Required] false [Type] Var List [Default Value] none [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 [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [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 [Valid Values]

Output: ECMAScript Variable

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 [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. [Valid Values]

Output: Connection IDs

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 [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. [Valid Values]

Output: Conference IDs

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [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 . [Valid Values]

Output: both dialogtransmit dialogreceive

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [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. [Valid Values]

Output: A valid time value for the HTTP 1.1 request [RFC2616]

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [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. [Valid Values]

Output: A valid time value for the HTTP 1.1 request [RFC2616]

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 [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. [Valid Values]

Output: valid media encoding type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [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. [Valid Values]

Output: get post

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [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. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


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

Output: Date and Time


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

Output: Date


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

Output: Month