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

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Specification

OWL 2 Web Ontology Language Document Overview


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

Output: For Users

OWL 2 Web Ontology Language Document Overview


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

Output: For Users

OWL 2 Web Ontology Language Document Overview


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

Output: For Users

OWL 2 Web Ontology Language Document Overview


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

Output: Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Specification

OWL 2 Web Ontology Language Document Overview


Input: [Section] Terminology [Feature/Operation] propID [Key Word] MUST

Output: propID uniquely identifies any privacy proposal

Explanation (or Implication if not supported)


Input: [Section] Data transport [Feature/Operation] the HTML LINK tag [Key Word] MUST

Output: agents and services must be able to locate a proposal in this location

Explanation (or Implication if not supported)


Input: [Feature/Operation] the HTTP extension mechanism [Key Word] MUST

Output: agents and services must be able to locate a proposal in this location

Explanation (or Implication if not supported)


Input: [Section] XML/RDF encoding [Feature/Operation] XML parsing [Key Word] MUST

Output: proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model.

Explanation (or Implication if not supported)


Input: [Section] XML/RDF encoding [Feature/Operation] Full XML and XML-namespace support [Key Word] MUST

Output: implementations must support full XML and namespaces, not just that used here.

Explanation (or Implication if not supported)


Input: [Section] Data References [Feature/Operation] base data reference syntax [Key Word] MUST

Output: agents must be able to understand that syntax of solicited information

Explanation (or Implication if not supported)


Input: [Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary [Key Word] MUST

Output: see the harmonized vocabulary [HARMV] for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure

Explanation (or Implication if not supported)


Input: [Section] Reason Codes [Feature/Operation] (OK, SRY-, ERR-, SRY, ERR) [Key Word] MUST

Output: necessary for reaching agreement.

Explanation (or Implication if not supported)


Input: [Feature/Operation] propID repository [Key Word] SHOULD

Output: full proposals can be compactly represented, new negotiation and agreement are not necessary if an agreement already exists.

Explanation (or Implication if not supported)


Input: [Feature/Operation] data repository [Key Word] MAY

Output: frequently requested user profile information is stored and managed by the user.

Explanation (or Implication if not supported)


Input: [Section] Data Definitions [Feature/Operation] new schema instantiation [Key Word] MAY

Output: schemas other than the base set can be instantiated and supported by the agent.

Explanation (or Implication if not supported)


Input: [Section] Source Attribute [Feature/Operation] source attributes "matched-form" and "extension" [Key Word] MAY

Output: agents support multiple, extensible mechanisms by which information is solicited.

Explanation (or Implication if not supported)


Input: [Event handler] onabort [Event handler event type]

Output: abort


Input: [Event handler] oncanplay [Event handler event type]

Output: canplay


Input: [Event handler] oncanplaythrough [Event handler event type]

Output: canplaythrough


Input: [Event handler] onchange [Event handler event type]

Output: change


Input: [Event handler] onclick [Event handler event type]

Output: click


Input: [Event handler] oncontextmenu [Event handler event type]

Output: contextmenu


Input: [Event handler] ondblclick [Event handler event type]

Output: dblclick


Input: [Event handler] ondrag [Event handler event type]

Output: drag


Input: [Event handler] ondragend [Event handler event type]

Output: dragend


Input: [Event handler] ondragenter [Event handler event type]

Output: dragenter


Input: [Event handler] ondragleave [Event handler event type]

Output: dragleave


Input: [Event handler] ondragover [Event handler event type]

Output: dragover


Input: [Event handler] ondragstart [Event handler event type]

Output: dragstart


Input: [Event handler] ondrop [Event handler event type]

Output: drop


Input: [Event handler] ondurationchange [Event handler event type]

Output: durationchange


Input: [Event handler] onemptied [Event handler event type]

Output: emptied


Input: [Event handler] onended [Event handler event type]

Output: ended


Input: [Event handler] onformchange [Event handler event type]

Output: formchange


Input: [Event handler] onforminput [Event handler event type]

Output: forminput


Input: [Event handler] oninput [Event handler event type]

Output: input


Input: [Event handler] oninvalid [Event handler event type]

Output: invalid


Input: [Event handler] onkeydown [Event handler event type]

Output: keydown


Input: [Event handler] onkeypress [Event handler event type]

Output: keypress


Input: [Event handler] onkeyup [Event handler event type]

Output: keyup


Input: [Event handler] onloadeddata [Event handler event type]

Output: loadeddata


Input: [Event handler] onloadedmetadata [Event handler event type]

Output: loadedmetadata


Input: [Event handler] onloadstart [Event handler event type]

Output: loadstart


Input: [Event handler] onmousedown [Event handler event type]

Output: mousedown


Input: [Event handler] onmousemove [Event handler event type]

Output: mousemove


Input: [Event handler] onmouseout [Event handler event type]

Output: mouseout


Input: [Event handler] onmouseover [Event handler event type]

Output: mouseover


Input: [Event handler] onmouseup [Event handler event type]

Output: mouseup


Input: [Event handler] onmousewheel [Event handler event type]

Output: mousewheel


Input: [Event handler] onpause [Event handler event type]

Output: pause


Input: [Event handler] onplay [Event handler event type]

Output: play


Input: [Event handler] onplaying [Event handler event type]

Output: playing


Input: [Event handler] onprogress [Event handler event type]

Output: progress


Input: [Event handler] onratechange [Event handler event type]

Output: ratechange


Input: [Event handler] onreadystatechange [Event handler event type]

Output: readystatechange


Input: [Event handler] onreset [Event handler event type]

Output: reset


Input: [Event handler] onseeked [Event handler event type]

Output: seeked


Input: [Event handler] onseeking [Event handler event type]

Output: seeking


Input: [Event handler] onselect [Event handler event type]

Output: select


Input: [Event handler] onshow [Event handler event type]

Output: show


Input: [Event handler] onstalled [Event handler event type]

Output: stalled


Input: [Event handler] onsubmit [Event handler event type]

Output: submit


Input: [Event handler] onsuspend [Event handler event type]

Output: suspend


Input: [Event handler] ontimeupdate [Event handler event type]

Output: timeupdate


Input: [Event handler] onvolumechange [Event handler event type]

Output: volumechange


Input: [Event handler] onwaiting [Event handler event type]

Output: waiting


Input: [EXI Option] alignment [Description] Alignment of event codes and content items [Default Value]

Output: bit-packed

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Document


Input: [EXI Option] compression [Description] EXI compression is used to achieve better compactness [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] strict [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] fragment [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] preserve [Description] Specifies whether comments, pis, etc. are preserved [Default Value]

Output: all false

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] selfContained [Description] Enables self-contained elements [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] schemaID [Description] Identify the schema information, if any, used to encode the body [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] datatypeRepresentationMap [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] blockSize [Description] Specifies the block size used for EXI compression [Default Value]

Output: 1,000,000

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] valueMaxLength [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value]

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] valuePartitionCapacity [Description] Specifies the total capacity of value partitions in a string table [Default Value]

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] [user defined meta-data] [Description] User defined meta-data may be added [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0


Input: [name] accesskey [values] list of key labels [description]

Output: A key label or list of key labels with which to associate the element; each key label represents a keyboard shortcut which UAs can use to activate the element or give focus to the element. An ordered set of unique space-separated tokens, each of which must be exactly one Unicode code point in length.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] class [values] set of space-separated tokens [description]

Output: A name of a classification, or list of names of classifications, to which the element belongs.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] contenteditable [values] "true" or "false" or "" (empty string) or empty [description]

Output: Specifies whether the contents of the element are editable.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] contextmenu [values] ID reference [description]

Output: The value of the id attribute on the menu with which to associate the element as a context menu.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] dir [values] "ltr" or "rtl" [description]

Output: Specifies the element’s text directionality.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] draggable [values] "true" or "false" [description]

Output: Specifies whether the element is draggable.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] hidden [values] "hidden" or "" (empty string) or empty [description]

Output: Specifies that the element represents an element that is not yet, or is no longer, relevant.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] id [values] ID [description]

Output: A unique identifier for the element. There must not be multiple elements in a document that have the same id value. Any string, with the following restrictions: 1. must be at least one character long 2. must not contain any space characters

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] lang [values] language tag [description]

Output: Specifies the primary language for the contents of the element and for any of the element’s attributes that contain text. A valid language tag, as defined in [BCP47].

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] spellcheck [values] "true" or "false" or "" (empty string) or empty [description]

Output: Specifies whether the element represents an element whose contents are subject to spell checking and grammar checking.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] style [values] string [description]

Output: Specifies zero or more CSS declarations that apply to the element [CSS].

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] tabindex [values] integer [description]

Output: Specifies whether the element represents an element that is is focusable (that is, an element which is part of the sequence of focusable elements in the document), and the relative order of the element in the sequence of focusable elements in the document.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] title [values] normal character data [description]

Output: Advisory information associated with the element.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [name] translate [values] "yes" or "no" [description]

Output: Specifies whether an element's attribute values and the values of its Text node children are to be translated when the page is localized, or whether to leave them unchanged.

HTML/Attributes/ Global - Web Education Community Group

Table of Core Attributes


Input: [Attribute Name] next [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] method [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] fetchid [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] synch [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] timeout [Details]

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

Voice Browser Call Control: CCXML Version 1.0


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Common Field Names] name [Definitions]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connid [Definitions]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] protocol* [Definitions]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] info* [Definitions]

Output: this property provides a reference to an object which may contain platform or protocol dependent information specific to the event

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] reason* [Definitions]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Common Field Names] connection [Definitions]

Output: an ECMAScript object reference to the Connection object identified by the connid property for this event

Voice Browser Call Control: CCXML Version 1.0


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

EXI Options in Options Field


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

EXI Options in Options Field


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

EXI Options in Options Field


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

EXI Options in Options Field


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether comments, pis, etc. are preserved

EXI Options in Options Field


Input: [EXI Option] selfContained [Default Value] false [Description]

Output: Enables self-contained elements

EXI Options in Options Field


Input: [EXI Option] schemaID [Default Value] none [Description]

Output: Identify the schema information, if any, used to encode the body

EXI Options in Options Field


Input: [EXI Option] datatypeRepresentationMap [Default Value] none [Description]

Output: Identify datatype representations used to encode values in EXI body

EXI Options in Options Field


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

EXI Options in Options Field


Input: [EXI Option] valueMaxLength [Default Value] unbounded [Description]

Output: Specifies the maximum string length of value content items to be considered for addition to the string table.

EXI Options in Options Field


Input: [EXI Option] valuePartitionCapacity [Default Value] unbounded [Description]

Output: Specifies the total capacity of value partitions in a string table

EXI Options in Options Field


Input: [EXI Option] [user defined] [Default Value] none [Description]

Output: User defined options may be added

EXI Options in Options Field


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

Output: Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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


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


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


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

Output: see prose


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

Output: width* of containing block


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

Output: width* of containing block


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


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


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


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


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

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


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

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


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


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


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


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

Output: width* of containing block


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

Output: width* of containing block


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


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

Output: Width and height of border box


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


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

Output: refer to width of containing block


Input: [0] CHARACTER [2] BOOLEAN [1]

Output: DECIMAL

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] CHARACTER VARYING [2] DATE [1]

Output: SMALLINT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] CHARACTER LARGE OBJECT [2] TIME [1]

Output: INTEGER

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] BINARY [2] TIMESTAMP [1]

Output: BIGINT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] BINARY VARYING [2] INTERVAL [1]

Output: FLOAT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] BINARY LARGE OBJECT [1]

Output: REAL

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] NUMERIC [1]

Output: DOUBLE PRECISION

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


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

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party is the issuer of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: The Party is the recipient of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to be attributed

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to obtain consent from

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to be informed of all uses

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party is the recipient of the compensation

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party is the usage tracker

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Function] op:to [Meaning]

Output: Returns the sequence containing every xs:integer between the values of the operands.

XQuery 1.0 and XPath 2.0 Functions and Operators


Input: [Function] fn:id [Meaning]

Output: Returns the sequence of element nodes having an ID value matching the one or more of the supplied IDREF values.

XQuery 1.0 and XPath 2.0 Functions and Operators


Input: [Function] fn:idref [Meaning]

Output: Returns the sequence of element or attribute nodes with an IDREF value matching one or more of the supplied ID values.

XQuery 1.0 and XPath 2.0 Functions and Operators


Input: [Function] fn:doc [Meaning]

Output: Returns a document node retrieved using the specified URI.

XQuery 1.0 and XPath 2.0 Functions and Operators


Input: [Function] fn:doc-available [Meaning]

Output: Returns true if a document node can be retrieved using the specified URI.

XQuery 1.0 and XPath 2.0 Functions and Operators


Input: [Function] fn:collection [Meaning]

Output: Returns a sequence of nodes retrieved using the specified URI or the nodes in the default collection.

XQuery 1.0 and XPath 2.0 Functions and Operators


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

Output: DISTINCT


Input: [Patterns] Property path expression [Query Forms] CONSTRUCT [Other] SERVICE [Modifiers]

Output: REDUCED


Input: [Patterns] Property path patterns [Query Forms] DESCRIBE [Modifiers]

Output: Projection


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

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Patterns] GRAPH [Modifiers]

Output: Select expressions


Input: [Id: Title] melton5 : A Tool vs A Kit to Build a Tool [State] no decision (accepted) [Type]

Output: request


Input: [Id: Title] kay2 : Allow description with the discussion element [State] no decision (raised) [Type]

Output: request


Input: [Id: Title] melton1 : Useless and confusing self-referencing link [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton2 : Inability to submit comments using the ExIT system [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton3 : Unclear form field when attempting to "Create new issue from scratch" [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton4 : Unclear structure of XML document containing the actual issues [State] agreed [Ack.] No reply from reviewer [Type]

Output: editorial


Input: [Id: Title] ashok-1 : Global variable or parameter "uri-to-issues-xml" cannot be defined more than once with the same import precedence [State] agreed [Ack.] No reply from reviewer [Type]

Output: error


Input: [Id: Title] kay1 : Recording follow-up discussions [State] agreed [Ack.] No reply from reviewer [Type]

Output: request


Input: [Id: Title] jacobs1 : Switch to UTF-8 in /2004 space [State] agreed [Ack.] No reply from reviewer [Type]

Output: request


Input: [Id: Title] walsh1 : Proposed ExIT schema improvements [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Security Issue] Confidentiality [Comments] The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however. [Requirement]

Output: Some

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Request Authentication [Comments] A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service. [Requirement]

Output: Some

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Response Authentication [Comments] An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication. [Requirement]

Output: Most

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Persistent Authentication [Comments] Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications. [Requirement]

Output: Some

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Message Correspondence [Comments] The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used. [Requirement]

Output: All

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Request Replayy [Comments] Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack. [Requirement]

Output: Some

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Denial of Service [Comments] Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks. [Requirement]

Output: Most

XML Key Management Specification (XKMS) Bindings


Input: [Property] bookmark-label [Values] content | | [Initial] content [Applies to] all elements [Inh.] no [Percentages] N/A [Media]

Output: all

CSS3 module: Generated Content for Paged Media


Input: [Property] bookmark-level [Values] none | [Initial] none [Applies to] all elements [Inh.] no [Percentages] N/A [Media]

Output: all

CSS3 module: Generated Content for Paged Media


Input: [Property] bookmark-target [Values] self | | [Initial] self [Applies to] all elements [Inh.] no [Percentages] N/A [Media]

Output: all

CSS3 module: Generated Content for Paged Media


Input: [Property] border-width [Values] | auto [Initial] auto [Applies to] @footnote areas [Inh.] no [Percentages] refer to normal length of horizontal border of footnote area [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-after [Initial] 2 [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-before [Initial] 2 [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-character [Initial] A string consisting of the Unicode hyphen character U+2010 [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-dictionary [Values] auto | [Initial] auto [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-lines [Values] none | [Initial] none [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate [Values] none | auto [Initial] none [Applies to] all elements [Inh.] yes [Percentages] N/A [Media]

Output: visual

CSS3 module: Generated Content for Paged Media


Input: [Property] string-set [Values] [[ ] [, ]* ] | none [Initial] none [Applies to] all elements [Inh.] no [Percentages] N/A [Media]

Output: all

CSS3 module: Generated Content for Paged Media


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

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


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

Output: PCDATA


Input: [0] Dependencies [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [Payload Security]

Output: Authentication defined by XKMS specification, client does not need to implement a comprehensive framework.

XML Key Management Specification (XKMS) Bindings


Input: [0] Use of XML Signature [Transaction Layer Security] Not required [Payload Security]

Output: Uses XML Signature in Enveloped Mode requiring slightly more complex processing.

XML Key Management Specification (XKMS) Bindings


Input: [0] Support for Routing [Transaction Layer Security] None [Payload Security]

Output: Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported.

XML Key Management Specification (XKMS) Bindings


Input: [0] Support for Confidentiality [Transaction Layer Security] Supported [Payload Security]

Output: None, although applications may employ TLS to establish a secure channel

XML Key Management Specification (XKMS) Bindings


Input: [0] Non-Repudiation [Transaction Layer Security] Requires additional payload security [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Bindings


Input: [0] Unspecified Party Authentication [Transaction Layer Security] Requires additional payload security [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Bindings


Input: [0] Client Authentication [Transaction Layer Security] Supported through certificate client authentication or through use of payload security. [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Bindings


Input: [Requirement Name] R-CsvValidation [Davide's Comments] "This requirement is also related to R-ExternalDataDefinitionResource, but it adds to the functional part." [Eric's Comments] Recommend Acceptance [Jeremy's Comments] Accept [Definition]

Output: Ability to validate a CSV for conformance with a specified metadata definition

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToRdfTransformation [Eric's Comments] Recommend removing. Is this perhaps a best practice as opposed to a requirement? [Jeremy's Comments] Retain this requirement - this underpins the function to be able to transform CSV into a different encoding [Definition]

Output: Ability to automatically transform a CSV into RDF

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToJsonTransformation [Eric's Comments] Recommend removing. Is this perhaps a best practice as opposed to a requirement? [Jeremy's Comments] Retain this requirement - this underpins the function to be able to transform CSV into a different encoding [Definition]

Output: Ability to automatically transform a CSV into JSON

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToXmlTransformation [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments] New [Definition]

Output: Ability to transform a CSV into XML

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CanonicalMappingInLieuOfAnnotation [Eric's Comments] "This seems to be related to R-CsvToRdfTransformation, R-CsvToJsonTransformation. If these two are kept does this requirement go away?" [Jeremy's Comments] "This is intended to fulfil the requirement to transform a CSV file (to RDF, JSON or other!) when there is no additional metadata annotation available ... retain this requirement" [Definition]

Output: Ability to transform CSV conforming to the core tabular data model yet lacking further annotation into a object / object graph serialisation

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-IndependentMetadataPublication [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments] New [Definition]

Output: Ability to publish metadata independently from the tabular data resource it describes.

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-SpecificationOfPropertyValuePairForEachRow [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments] New [Definition]

Output: Ability to define a property-value pair for inclusion in each row.

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-ConditionalProcessingBasedOnCellValues [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments] New [Definition]

Output: Ability to apply conditional processing based on the value of a specific cell.

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CommentLines [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments] New [Definition]

Output: Ability to identify comment lines within a CSV file and skip over them during parsing, format conversion or other processing.

Requirements analysis - CSV on the Web Working Group Wiki


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

Output: DISTINCT


Input: [Patterns] Property path expression [Query Forms] CONSTRUCT [Other] SERVICE [Modifiers]

Output: REDUCED


Input: [Patterns] Property path patterns [Query Forms] DESCRIBE [Modifiers]

Output: Projection


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

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Patterns] GRAPH [Modifiers]

Output: Select expressions


Input: [Property] bookmark-label [Values] content | | [Initial] content [Applies to] all elements [Percentages] N/A [Media] all [Inh.]

Output: no

CSS3 module: Generated Content for Paged Media


Input: [Property] bookmark-level [Values] none | [Initial] none [Applies to] all elements [Percentages] N/A [Media] all [Inh.]

Output: no

CSS3 module: Generated Content for Paged Media


Input: [Property] bookmark-target [Values] self | | [Initial] self [Applies to] all elements [Percentages] N/A [Media] all [Inh.]

Output: no

CSS3 module: Generated Content for Paged Media


Input: [Property] border-width [Values] | auto [Initial] auto [Applies to] @footnote areas [Percentages] refer to normal length of horizontal border of footnote area [Media] visual [Inh.]

Output: no

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-after [Initial] 2 [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-before [Initial] 2 [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-character [Initial] A string consisting of the Unicode hyphen character U+2010 [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-dictionary [Values] auto | [Initial] auto [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate-lines [Values] none | [Initial] none [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] hyphenate [Values] none | auto [Initial] none [Applies to] all elements [Percentages] N/A [Media] visual [Inh.]

Output: yes

CSS3 module: Generated Content for Paged Media


Input: [Property] string-set [Values] [[ ] [, ]* ] | none [Initial] none [Applies to] all elements [Percentages] N/A [Media] all [Inh.]

Output: no

CSS3 module: Generated Content for Paged Media


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


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

Output: App server returns initial page to device


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

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


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

Output: Device handles location information


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

Output: Touch screen detects and processes input


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

Output: ASR Server receives request and establishes connection


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

Output: ASR Server processes speech and returns results to device


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

Output: App Server processes input and returns data to device


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

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


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

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


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

Output: App Server processes input and returns data to device


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

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


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

Output: App Server processes input and returns data to device


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

Output: ASR Server receives request and establishes connection


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

Output: ASR Server processes speech and returns results to device


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

Output: App server responds with appropriate dialog


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

Output: App Server processes input and returns data to device


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

Output: Required but not dependent

XML Key Management Specification (XKMS) Bindings


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

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

XML Key Management Specification (XKMS) Bindings


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

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

XML Key Management Specification (XKMS) Bindings


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

Output: Required but not dependent

XML Key Management Specification (XKMS) Bindings


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

Output: Required but not dependent

XML Key Management Specification (XKMS) Bindings


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

Output: Unnecessary

XML Key Management Specification (XKMS) Bindings


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

Output: Unnecessary

XML Key Management Specification (XKMS) Bindings


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

Output: Unnecessary

XML Key Management Specification (XKMS) Bindings


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [Security Issue] Confidentiality [Requirement] Some [Comments]

Output: The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Request Authentication [Requirement] Some [Comments]

Output: A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Response Authentication [Requirement] Most [Comments]

Output: An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Persistent Authentication [Requirement] Some [Comments]

Output: Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Message Correspondence [Requirement] All [Comments]

Output: The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Request Replayy [Requirement] Some [Comments]

Output: Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack.

XML Key Management Specification (XKMS) Bindings


Input: [Security Issue] Denial of Service [Requirement] Most [Comments]

Output: Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks.

XML Key Management Specification (XKMS) Bindings


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: [Name] target [Required] false [Attribute Constraints] Must not occur with 'targetexpr' [Type] URI [Default Value] none [Description] The unique identifier of the message target that the platform should send the event to. See 6.2.4 The Target of Send for details. [Valid Values]

Output: A valid target URI

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


Input: [Name] targetexpr [Required] false [Attribute Constraints] Must not occur with 'target' [Type] Value expression [Default Value] none [Description] A dynamic alternative to 'target'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'target'. [Valid Values]

Output: An expression evaluating to a valid target URI

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


Input: [Name] id [Required] false [Attribute Constraints] Must not occur with 'idlocation'. [Type] xml:ID [Default Value] none [Description] A string literal to be used as the identifier for this instance of . See 3.14 IDs for details. [Valid Values]

Output: Any valid token

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


Input: [Name] idlocation [Required] false [Attribute Constraints] Must not occur with 'id'. [Type] Location expression [Default Value] none [Description] Any location expression evaluating to a data model location in which a system-generated id can be stored. See below for details. [Valid Values]

Output: Any valid location expression

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


Input: [Name] delay [Required] false [Attribute Constraints] Must not occur with 'delayexpr' or when the attribute 'target' has the value "_internal". [Type] Duration.datatype [Default Value] None [Description] Indicates how long the processor should wait before dispatching the message. See E Schema for details on the data type. [Valid Values]

Output: A time designation as defined in CSS2 [CSS2] format

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


Input: [Name] delayexpr [Required] false [Attribute Constraints] Must not occur with 'delay' or when the attribute 'target' has the value "_internal". [Type] Value expression [Default Value] None [Description] A dynamic alternative to 'delay'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'delay'. [Valid Values]

Output: A value expression which returns a time designation as defined in CSS2 [CSS2] format

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


Input: [Name] namelist [Required] false [Attribute Constraints] Must not be specified in conjunction with element. [Type] List of location expressions [Default Value] none [Description] A space-separated list of one or more data model locations to be included as attribute/value pairs with the message. (The name of the location is the attribute and the value stored at the location is the value.) See 5.9.2 Location Expressions for details. [Valid Values]

Output: List of data model locations

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


Input: [Name] event [Required] false [Attribute Constraints] Must not occur with 'eventexpr'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'eventexpr' must be present. [Type] EventType.datatype [Default Value] none [Description]

Output: A string indicating the name of message being generated. See E Schema for details on the data type.

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


Input: [Name] eventexpr [Required] false [Attribute Constraints] Must not occur with 'event'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'event' must be present. [Type] Value expression [Default Value] none [Description]

Output: A dynamic alternative to 'event'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'event'.

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


Input: [Name] target [Required] false [Attribute Constraints] Must not occur with 'targetexpr' [Type] URI [Default Value] none [Valid Values] A valid target URI [Description]

Output: The unique identifier of the message target that the platform should send the event to. See 6.2.4 The Target of Send for details.

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


Input: [Name] targetexpr [Required] false [Attribute Constraints] Must not occur with 'target' [Type] Value expression [Default Value] none [Valid Values] An expression evaluating to a valid target URI [Description]

Output: A dynamic alternative to 'target'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'target'.

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


Input: [Name] type [Required] false [Attribute Constraints] Must not occur with 'typeexpr' [Type] URI [Default Value] none [Description]

Output: The URI that identifies the transport mechanism for the message. See 6.2.5 The Type of Send for details.

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


Input: [Name] typeexpr [Required] false [Attribute Constraints] Must not occur with 'type' [Type] value expression [Default Value] none [Description]

Output: A dynamic alternative to 'type'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'type'.

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


Input: [Name] id [Required] false [Attribute Constraints] Must not occur with 'idlocation'. [Type] xml:ID [Default Value] none [Valid Values] Any valid token [Description]

Output: A string literal to be used as the identifier for this instance of . See 3.14 IDs for details.

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


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

Output: Any location expression evaluating to a data model location in which a system-generated id can be stored. See below for details.

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


Input: [Name] delay [Required] false [Attribute Constraints] Must not occur with 'delayexpr' or when the attribute 'target' has the value "_internal". [Type] Duration.datatype [Default Value] None [Valid Values] A time designation as defined in CSS2 [CSS2] format [Description]

Output: Indicates how long the processor should wait before dispatching the message. See E Schema for details on the data type.

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


Input: [Name] delayexpr [Required] false [Attribute Constraints] Must not occur with 'delay' or when the attribute 'target' has the value "_internal". [Type] Value expression [Default Value] None [Valid Values] A value expression which returns a time designation as defined in CSS2 [CSS2] format [Description]

Output: A dynamic alternative to 'delay'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'delay'.

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


Input: [Name] namelist [Required] false [Attribute Constraints] Must not be specified in conjunction with element. [Type] List of location expressions [Default Value] none [Valid Values] List of data model locations [Description]

Output: A space-separated list of one or more data model locations to be included as attribute/value pairs with the message. (The name of the location is the attribute and the value stored at the location is the value.) See 5.9.2 Location Expressions for details.

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


Input: [Requirement] Some [Comments] The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however. [Security Issue]

Output: Confidentiality

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] Some [Comments] A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service. [Security Issue]

Output: Request Authentication

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] Most [Comments] An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication. [Security Issue]

Output: Response Authentication

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] Some [Comments] Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications. [Security Issue]

Output: Persistent Authentication

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] All [Comments] The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used. [Security Issue]

Output: Message Correspondence

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] Some [Comments] Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack. [Security Issue]

Output: Request Replayy

XML Key Management Specification (XKMS) Bindings


Input: [Requirement] Most [Comments] Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks. [Security Issue]

Output: Denial of Service

XML Key Management Specification (XKMS) Bindings


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [0] Dependencies [Payload Security] Authentication defined by XKMS specification, client does not need to implement a comprehensive framework. [Transaction Layer Security]

Output: Authentication mechanism defined by TLS which clients must implement

XML Key Management Specification (XKMS) Bindings


Input: [0] Use of XML Signature [Payload Security] Uses XML Signature in Enveloped Mode requiring slightly more complex processing. [Transaction Layer Security]

Output: Not required

XML Key Management Specification (XKMS) Bindings


Input: [0] Support for Routing [Payload Security] Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported. [Transaction Layer Security]

XML Key Management Specification (XKMS) Bindings


Input: [0] Support for Confidentiality [Payload Security] None, although applications may employ TLS to establish a secure channel [Transaction Layer Security]

Output: Supported

XML Key Management Specification (XKMS) Bindings


Input: [0] Non-Repudiation [Payload Security] Supported [Transaction Layer Security]

Output: Requires additional payload security

XML Key Management Specification (XKMS) Bindings


Input: [0] Unspecified Party Authentication [Payload Security] Supported [Transaction Layer Security]

Output: Requires additional payload security

XML Key Management Specification (XKMS) Bindings


Input: [0] Client Authentication [Payload Security] Supported [Transaction Layer Security]

Output: Supported through certificate client authentication or through use of payload security.

XML Key Management Specification (XKMS) Bindings


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Description] HTTP Request to app server [Event Handler] App server returns initial page to device [Resulting Action]

Output: Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification).


Input: [User Action/External Input] User interacts in an authentication dialog [Action on Device] Device executes authentication dialog using local ASR processing [Event Description] HTTP Request to app server which includes user credentials [Event Handler] App server returns initial page to device including user preferences [Resulting Action]

Output: User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application)


Input: [User Action/External Input] Initial GPS Input [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device handles location information [Resulting Action]

Output: Device updates map on graphical display (assumes all maps are stored locally on device)


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

Output: Volume indicator changes on screen. Volume of speech output is changed


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Device initiates connection to ASR server [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action]

Output: "listening" icon appears on display (utterances prior to establishing the connection are buffered)


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

Output: Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


Input: [User Action/External Input] GPS Input at regular intervals [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action]

Output: Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user


Input: [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and determines that user is off course [Resulting Action]

Output: Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated


Input: [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


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

Output: User is informed of traffic conditions and asked whether route should be recalculated.


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action]

Output: User hears acknowledgement prompt for continuation, and "listening" icon appears on display


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

Output: Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action]

Output: User interacts in a dialog and selects destination. User is asked whether this is a new destination


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with new route and directions highlighting next step


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

Output: Service is initiated and GPS satellite detection begins


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

Output: Device executes authentication dialog using local ASR processing


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


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


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

Output: Device initiates connection to ASR server


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


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

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


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


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


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

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


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