Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Required] No [Default Value] None [Name]

Output: maxage

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: Attributes


Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Required] No [Default Value] None [Name]

Output: maxstale

Voice Extensible Markup Language (VoiceXML) 3.0

Table 12: Attributes


Input: [Name] confidencelevel [Default] 0.5 [Description]

Output: The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Name] sensitivity [Default] 0.5 [Description]

Output: Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Name] speedvsaccuracy [Default] 0.5 [Description]

Output: A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Name] completetimeout [Default] platform-dependent [Description]

Output: The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations). See 8.3 Speech and DTMF Input Timing Properties. Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Name] incompletetimeout [Default] undefined? [Description]

Output: The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Name] maxspeechtimeout [Default] platform-dependent [Description]

Output: The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 91: Speech Recognition Properties


Input: [Evaluation] Bandwidth efficiency [Picture Element] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers] Yes, requests only what it needs [image-set CSS/uri templates]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [Picture Element] Yes [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Server-side config not required [Picture Element] Client based [Spacer background-image] Client based [Request headers] Server-config required [image-set CSS/uri templates]

Output: Client based


Input: [Evaluation] Structure Simplicity (HTML) [Picture Element] Difficult for beginners [Spacer background-image] Existing elements [Request headers] No changes [image-set CSS/uri templates]

Output: (structure not decided, only focuses on CSS)


Input: [Evaluation] Presentation Simplicity (CSS) [Picture Element] Yes [Spacer background-image] Heavy use of media queries [Request headers] No changes [image-set CSS/uri templates]

Output: Difficult for beginners, but consistent image-set for backgrounds


Input: [Evaluation] Easy of maintenance [Picture Element] Responsive scenarios within structure [Spacer background-image] Control image variants with CSS [Request headers] Server-side config [image-set CSS/uri templates]

Output: Control image variants with CSS


Input: [Evaluation] Separation of concerns [Picture Element] Presentation scenarios within structure [Spacer background-image] Control image variants with CSS [Request headers] Depends on implementation [image-set CSS/uri templates]

Output: Control image variants with CSS


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [Picture Element] Yes [Spacer background-image] No [Request headers] No [image-set CSS/uri templates]

Output: This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide.


Input: [Evaluation] Centralized image variants [Picture Element] Located within structure [Spacer background-image] Variants within media queries [Request headers] Depends on implementation [image-set CSS/uri templates]

Output: Variants formats within image-set() urls


Input: [Evaluation] Request static images [Picture Element] Yes [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Request dynamically resized images [Picture Element] Manually code dimensions within urls [Spacer background-image] Manually code dimensions within urls [Request headers] Yes [image-set CSS/uri templates]

Output: Request exact dimension needed


Input: [Evaluation] High-resolution when the device is capable [Picture Element] Yes, from media queries [Spacer background-image] Yes, from media queries [Request headers] Yes, but may be maintained by user agent [image-set CSS/uri templates]

Output: Yes, from image-set()


Input: [Evaluation] Adjusts to device bandwidth [Picture Element] Yes (if bandwidth added to media queries) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers] No [image-set CSS/uri templates]

Output: Yes (if bandwidth added to image-set)


Input: [Evaluation] Fallback for browsers without support [Picture Element] Yes, img within noscript [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: (no structure to evaluate)


Input: [Evaluation] Printable images [Picture Element] Yes [Spacer background-image] No [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Polyfill [Picture Element] Yes [Spacer background-image] Not needed [Request headers] Not needed [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Minimal structure updates for browser support [Picture Element] Create a new picture element [Spacer background-image] Not needed [Request headers] Heavy restructuring [image-set CSS/uri templates]

Output: (no structure to evaluate)


Input: [Evaluation] Minimal presentation updates for browser support [Picture Element] No new CSS required [Spacer background-image] Not needed [Request headers] No new CSS required [image-set CSS/uri templates]

Output: image-set being evaluated by webkit for background images


Input: [Evaluation] Image within content [Picture Element] Yes [Spacer background-image] No [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] No new file formats [Picture Element] Works with existing files [Spacer background-image] Works with existing files [Request headers] Works with existing files [image-set CSS/uri templates]

Output: Works with existing files


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Name] bargein [Type] boolean [Required] No [Default Value] bargein property [Description]

Output: Controls whether the prompt can be interrupted.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] bargeintype [Type] string [Required] No [Default Value] bargeintype property [Description]

Output: On prompts that can be interrupted, determines the type of bargein, either 'speech', or 'hotword'.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] cond [Type] data model expression [Required] No [Default Value] true [Description]

Output: A data model expression that must evaluate to true after conversion to boolean in order for the prompt to be played.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] count [Type] positive integer [Required] No [Default Value] 1 [Description]

Output: A number indicating the repetition count, allowing a prompt to be activated or not depending on the current repetition count.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] timeout [Type] Time Designation [Required] No [Default Value] timeout property [Description]

Output: The time to wait for user input.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] xml:lang [Type] string [Required] No [Default Value] document's "xml:lang" attribute [Description]

Output: The language identifier for the prompt.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] xml:base [Type] string [Required] No [Default Value] document's "xml:base" attribute [Description]

Output: Declares the base URI from which relative URIs in the prompt are resolved.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [.capture*] new non-modal prompt [2] form control derived from input file, part of the page [(resp audio, video)] new form control, part of the page [0]

Output: UI


Input: [.capture*] several new interfaces [2] limited (derive from FileReader) [(resp audio, video)] limited (derive from FileReader) [0]

Output: scope of new API


Input: [.capture*] can grant access to API without prompt [2] awkward to use [(resp audio, video)] awkward to use [0]

Output: In widgets


Input: [.capture*] left to the developer [2] possibly transparent (but down to the UA) [(resp audio, video)] possibly transparent (but down to the UA) [0]

Output: Integration with Media gallery


Input: [.capture*] new API calls needed [2] possibly transparent? [(resp audio, video)] possibly transparent? [0]

Output: viewfinder compat


Input: [.capture*] available in API [2] number controled by number of fields — awkward user exp; not clear how to control duration [(resp audio, video)] could be controled with attributes on the input field? [0]

Output: control on number and duration of captures


Input: [.capture*] possible with boolean flags added to Capture interface [2] not clear; might need flags addition [(resp audio, video)] not clear either [0]

Output: detection for support of capture capabilities


Input: [.capture*] need new API calls added to Capture [2] no clear path; probably would need API of its own, but not clear how to plug in [(resp audio, video)] no clear path; probably would need API of its own, but not clear how to plug in [0]

Output: evolution for more control of the capture devices


Input: [.capture*] None [2] Limited [(resp audio, video)] Not trivial [0]

Output: impact/dependence on markup spec (html5?)


Input: [Category] Navigation and click-stream data [Structure] uri [Short display name] URI of requested resource [loginfo]

Output: uri

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] date [Short display name] Request timestamp [loginfo]

Output: timestamp

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Computer Information [Structure] ipaddr [Short display name] Client's IP address or hostname [loginfo]

Output: clientip

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] HTTP request method [loginfo]

Output: other.httpmethod

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] Data bytes in response [loginfo]

Output: other.bytes

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Navigation and click-stream data [Structure] unstructured [Short display name] Response status code [loginfo]

Output: other.statuscode

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Name] EncodingError [Description]

Output: A path or URL supplied to the API was malformed.


Input: [Name] InvalidModificationError [Description]

Output: The modification requested was illegal. Examples of invalid modifications include moving a directory into its own child, moving a file into its parent directory without changing its name, or copying a directory to a path occupied by a file.


Input: [Name] InvalidStateError [Description]

Output: An operation depended on state cached in an interface object, but that state that has changed since it was read from disk. Which values will actually go stale? Modification time, name, more rarely type. If an atomic save [replacing a file with a new one of the same name] happens underneath, should we even be required to notice?


Input: [Name] NotFoundError [Description]

Output: A required file or directory could not be found at the time an operation was processed.


Input: [Name] NotReadableErr [Description]

Output: A required file or directory could be read.


Input: [Name] NoModificationAllowedError [Description]

Output: The user attempted to write to a file or directory which could not be modified due to the state of the underlying filesystem.


Input: [Name] PathExistsError [Description]

Output: The user agent failed to create a file or directory due to the existence of a file or directory with the same path.


Input: [Name] QuotaExceededError [Description]

Output: The operation failed because it would cause the application to exceed its storage quota.


Input: [Name] SecurityError [Description]

Output: A required file was unsafe for access within a Web application Too many calls are being made on filesystem resources This is a security error code to be used in situations not covered by any other error codes.


Input: [Name] TypeMismatchError [Description]

Output: The user has attempted to look up a file or directory, but the Entry found is of the wrong type [e.g. is a DirectoryEntry when the user requested a FileEntry].


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

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.4.2: Terms for the attribute “scope” of the entity Role


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

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [For this page] A plain text version of the page, handy for pasting into email. [,shortcut] ,text [Access control] Same as the document [General tool]

Output: HTML to Text converter


Input: [For this page] List of bad links in the page [,shortcut] ,checklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] Bad links in a page and in pages linked from it [,shortcut] ,rchecklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] List of HTML markup errors. [,shortcut] ,validate [Access control] Same as the document [General tool]

Output: HTML Validator


Input: [For this page] List of spelling errors. [,shortcut] ,spell [Access control] Same as the document [General tool]

Output: W3C Spellchecker


Input: [For this page] List of style CSS errors. [,shortcut] ,cssvalidate [Access control] Works only on public pages. [General tool]

Output: CSS Validator


Input: [For this page] Log of changes to the document [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [General tool]

Output: CVS Log


Input: [For this page] HTTP headers sent by the server [,shortcut] ,headers [Access control] Same as the document [General tool]

Output: Headers


Input: [For this page] Check the compliance of this document to the W3C publication rules [,shortcut] ,pubrules [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [For this page] Check the compliance of this document to the W3C publication rules, only displaying errors [,shortcut] ,pubruleserrors [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.


Input: [General tool] CSS Validator [,shortcut] ,cssvalidate [Access control] Works only on public pages. [For this page]

Output: List of style CSS errors.


Input: [General tool] CVS Log [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [For this page]

Output: Log of changes to the document


Input: [General tool] Headers [,shortcut] ,headers [Access control] Same as the document [For this page]

Output: HTTP headers sent by the server


Input: [General tool] the pubrules checker [,shortcut] ,pubrules [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules


Input: [General tool] the pubrules checker [,shortcut] ,pubruleserrors [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules, only displaying errors


Input: [For this page] A plain text version of the page, handy for pasting into email. [,shortcut] ,text [Access control] Same as the document [General tool]

Output: HTML to Text converter


Input: [For this page] List of bad links in the page [,shortcut] ,checklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] Bad links in a page and in pages linked from it [,shortcut] ,rchecklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] List of HTML markup errors. [,shortcut] ,validate [Access control] Same as the document [General tool]

Output: HTML Validator


Input: [For this page] List of spelling errors. [,shortcut] ,spell [Access control] Same as the document [General tool]

Output: W3C Spellchecker


Input: [For this page] List of style CSS errors. [,shortcut] ,cssvalidate [Access control] Works only on public pages. [General tool]

Output: CSS Validator


Input: [For this page] Log of changes to the document [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [General tool]

Output: CVS Log


Input: [For this page] HTTP headers sent by the server [,shortcut] ,headers [Access control] Same as the document [General tool]

Output: Headers


Input: [For this page] Check the compliance of this document to the W3C publication rules [,shortcut] ,pubrules [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [For this page] Check the compliance of this document to the W3C publication rules, only displaying errors [,shortcut] ,pubruleserrors [Access control] Same as the document [General tool]

Output: the pubrules checker


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

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Name] bargein [Description] Controls whether the prompt can be interrupted. [Required] No [Default Value] bargein property [Type]

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] bargeintype [Description] On prompts that can be interrupted, determines the type of bargein, either 'speech', or 'hotword'. [Required] No [Default Value] bargeintype property [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


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

Output: data model expression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] count [Description] A number indicating the repetition count, allowing a prompt to be activated or not depending on the current repetition count. [Required] No [Default Value] 1 [Type]

Output: positive integer

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] timeout [Description] The time to wait for user input. [Required] No [Default Value] timeout property [Type]

Output: Time Designation

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] xml:lang [Description] The language identifier for the prompt. [Required] No [Default Value] document's "xml:lang" attribute [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Name] xml:base [Description] Declares the base URI from which relative URIs in the prompt are resolved. [Required] No [Default Value] document's "xml:base" attribute [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 24: Attributes


Input: [Expected Values] alternativeText [Augmented Access Mode] Textual [Description] alternative text is provided for visual content (e.g., the HTML alt attribute).

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] longDescription [Augmented Access Mode] Textual [Description] descriptions are provided for image-based visual content and/or complex structures such as tables, mathematics, diagrams or charts.

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] ChemML laTex MathML [Augmented Access Mode] Textual [Description] The use of one of these specific ASCII/XML encodings for mathematics or chemistry. These can have extensions specified, but are rarely needed.

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] transcript [Augmented Access Mode] Textual [Description] The addition of a separate transcript to convey the meaning of the audio.

Output: Auditory

Source Access Mode (before augmentation)


Input: [Expected Values] captions [Augmented Access Mode] Visual [Description] The addition of synchronized text (closed captions) to convey the meaning of the audio. Note that while many captions may be implemented as textual in the transport, users think of them as being a visual appearance.

Output: Auditory

Source Access Mode (before augmentation)


Input: [Expected Values] signLanguage [Augmented Access Mode] Visual [Description] The presentation of audio in sign language in the visual presentation. The most likely extension is /sgn-en-us or other ISO 639 sign language code.

Output: Auditory

Source Access Mode (before augmentation)


Input: [Expected Values] audioDescription [Augmented Access Mode] Auditory [Description] Audio descriptions are available (e.g., via the HTML5 track element). Common extensions are for the various "onImage" refinements noted above.

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] braille [Augmented Access Mode] Tactile [Description] braille content or alternative is available (e.g., eBraille or print braille) This can have extensions for the different types of braille, /ASCII, /music, /math, /chem or /nemeth) (also consider /contracted and /gradeII or other nomenclature... pretty open)

Output: Visual or Textual

Source Access Mode (before augmentation)


Input: [Expected Values] tactileGraphic [Augmented Access Mode] Tactile [Description] tactile graphics have been provided, as described in the BANA Guidelines and Standards for Tactile Graphics.

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] tactileObject [Augmented Access Mode] Tactile [Description] tactile 3D objects have been defined and a 3D object or instructions to build one are available.

Output: Visual

Source Access Mode (before augmentation)


Input: [Parameter] propertyNames [Type] DOMString[] [Nullable] ✘ [Description] This argument identifies an array containing the properties for which the values need to be retrieved. For an empty array all properties carrying values will be retrieved. Optional arguments allow refining the request. [Optional]


Input: [Parameter] successCallback [Type] PropertyCallback [Nullable] ✘ [Description] This argument holds a callback object for asynchronous requests to the property. The successCallback object implements the PropertyCallback interface and holds a handleEvent operation that needs to be called once all data for the requested property is gathered. This handleEvent operation needs to be called with a new MediaAnnotation array. [Optional]


Input: [Parameter] errorCallback [Type] ErrorCallback [Nullable] ✘ [Description] This argument holds a callback object for failure of asynchronous requests to the property. The errorCallback object implements the ErrorCallback interface and holds a handleEvent operation that needs to be called if an attempt fails. This handleEvent operation needs to be called with a new DOMString representing the status code of the error (see Section 4.7 for details). [Optional]


Input: [Parameter] fragment [Type] DOMString [Nullable] ✘ [Description] This argument contains a URI identifying the specific media fragment for which the metadata is requested. The URI must conform to the URI for Media Fragment [MEDIA-FRAGMENTS] specification. This parameter is optional. [Optional]


Input: [Parameter] sourceFormat [Type] DOMString [Nullable] ✘ [Description] This argument identifies a specific metadata format. It should use the metadata format identifiers defined in the Ontology for Media Resources 1.0 specification [MEDIA-ONTOLOGY]. If a metadata format is defined, only the metadata available in the corresponding metadata format are retrieved. This parameter is optional. [Optional]


Input: [Parameter] language [Type] DOMString [Nullable] ✘ [Description] This argument allows to identify the language of the metadata. Values for the metadata will only be returned if it is available in the specified language. Recommended best practice is to use BCP 47 [BCP47]. This parameter is optional. [Optional]


Input: [Evaluation] Bandwidth efficiency [image-set CSS/uri templates] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers] Yes, requests only what it needs [Picture Element]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Server-side config not required [image-set CSS/uri templates] Client based [Spacer background-image] Client based [Request headers] Server-config required [Picture Element]

Output: Client based


Input: [Evaluation] Structure Simplicity (HTML) [image-set CSS/uri templates] (structure not decided, only focuses on CSS) [Spacer background-image] Existing elements [Request headers] No changes [Picture Element]

Output: Difficult for beginners


Input: [Evaluation] Presentation Simplicity (CSS) [image-set CSS/uri templates] Difficult for beginners, but consistent image-set for backgrounds [Spacer background-image] Heavy use of media queries [Request headers] No changes [Picture Element]

Output: Yes


Input: [Evaluation] Easy of maintenance [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers] Server-side config [Picture Element]

Output: Responsive scenarios within structure


Input: [Evaluation] Separation of concerns [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers] Depends on implementation [Picture Element]

Output: Presentation scenarios within structure


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [image-set CSS/uri templates] This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide. [Spacer background-image] No [Request headers] No [Picture Element]

Output: Yes


Input: [Evaluation] Centralized image variants [image-set CSS/uri templates] Variants formats within image-set() urls [Spacer background-image] Variants within media queries [Request headers] Depends on implementation [Picture Element]

Output: Located within structure


Input: [Evaluation] Request static images [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Request dynamically resized images [image-set CSS/uri templates] Request exact dimension needed [Spacer background-image] Manually code dimensions within urls [Request headers] Yes [Picture Element]

Output: Manually code dimensions within urls


Input: [Evaluation] High-resolution when the device is capable [image-set CSS/uri templates] Yes, from image-set() [Spacer background-image] Yes, from media queries [Request headers] Yes, but may be maintained by user agent [Picture Element]

Output: Yes, from media queries


Input: [Evaluation] Adjusts to device bandwidth [image-set CSS/uri templates] Yes (if bandwidth added to image-set) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers] No [Picture Element]

Output: Yes (if bandwidth added to media queries)


Input: [Evaluation] Fallback for browsers without support [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes, img within noscript


Input: [Evaluation] Printable images [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Polyfill [image-set CSS/uri templates] Yes [Spacer background-image] Not needed [Request headers] Not needed [Picture Element]

Output: Yes


Input: [Evaluation] Minimal structure updates for browser support [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Not needed [Request headers] Heavy restructuring [Picture Element]

Output: Create a new picture element


Input: [Evaluation] Minimal presentation updates for browser support [image-set CSS/uri templates] image-set being evaluated by webkit for background images [Spacer background-image] Not needed [Request headers] No new CSS required [Picture Element]

Output: No new CSS required


Input: [Evaluation] Image within content [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] No new file formats [image-set CSS/uri templates] Works with existing files [Spacer background-image] Works with existing files [Request headers] Works with existing files [Picture Element]

Output: Works with existing files


Input: [Attribute Type] CDATA [Definition]

Output: Character data

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREFS [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NAME [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKEN [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

XHTML™ Modularization 1.1 - Second Edition


Input: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.


Input: [General tool] CSS Validator [,shortcut] ,cssvalidate [Access control] Works only on public pages. [For this page]

Output: List of style CSS errors.


Input: [General tool] CVS Log [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [For this page]

Output: Log of changes to the document


Input: [General tool] Headers [,shortcut] ,headers [Access control] Same as the document [For this page]

Output: HTTP headers sent by the server


Input: [General tool] the pubrules checker [,shortcut] ,pubrules [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules


Input: [General tool] the pubrules checker [,shortcut] ,pubruleserrors [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules, only displaying errors


Input: [loginfo] uri [Category] Navigation and click-stream data [Structure] uri [Short display name]

Output: URI of requested resource

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] timestamp [Category] Navigation and click-stream data [Structure] date [Short display name]

Output: Request timestamp

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] clientip [Category] Computer Information [Structure] ipaddr [Short display name]

Output: Client's IP address or hostname

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.httpmethod [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: HTTP request method

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.bytes [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: Data bytes in response

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [loginfo] other.statuscode [Category] Navigation and click-stream data [Structure] unstructured [Short display name]

Output: Response status code

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


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

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6535 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters 4 Phases of Serialization 5.1.4 XML Output Method: the indent and suppress-indentation Parameters 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 8.1.4 Text Output Method: the indent and suppress-indentation Parameters [Description of change]

Output: Added definition of the suppress-indentation serialization parameter.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7829 [Erratum (if applicable)] SE.E14 [Category] Substantive [Affected sections] 7.2 Writing Attributes [Description of change]

Output: Clarified how minimized attributes are handled under the rules of the HTML output method.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8245 [Erratum (if applicable)] SE.E15 [Category] Editorial [Affected sections] 7.3 Writing Character Data C Summary of Error Conditions [Description of change]

Output: Corrected description of a serialization error that mentions which control characters are not permitted under the rules of the HTML output method

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7823 [Erratum (if applicable)] SE.E16 [Category] Substantive [Affected sections] 7.1 Markup for Elements [Description of change]

Output: Clarified how the script and style elements are handled for the HTML output method.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8651 [Erratum (if applicable)] SE.E17 [Category] Substantive [Affected sections] 1.1 Terminology 6.1.14 XHTML Output Method: the include-content-type Parameter 7.1 Markup for Elements 7.2 Writing Attributes 7.4.13 HTML Output Method: the include-content-type Parameter [Description of change]

Output: Clarified what it means to compare without regard to case.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8206 [Erratum (if applicable)] SE.E18 [Category] Editorial [Affected sections] 4 Phases of Serialization [Description of change]

Output: Clarified what it means to escape according to HTML or XML rules.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6808 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 5.1.4 XML Output Method: the indent and suppress-indentation Parameters [Description of change]

Output: Relaxed rules for the XML output method that specify where a serializer is permitted to add whitespace. This introduces an incompatibility only inasmuch as the serialized results produced by a serializer conforming to this specification could differ from the results a serializer that adheres to [XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)] would be permitted to produce.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla bug 9302 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Defined a mechanism for specifying serialization parameter settings in the form of a data model instance.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Description of change]

Output: Replaced all uses of the words legal and illegal with more appropriate terms.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [postal] name [Structure] personname [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] street [Structure] unstructured [Short display name] Street Address [Category]

Output: Physical Contact Information

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] city [Structure] unstructured [Short display name] City [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] stateprov [Structure] unstructured [Short display name] State or Province [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] postalcode [Structure] unstructured [Short display name] Postal Code [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] country [Structure] unstructured [Short display name] Country Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [postal] organization [Structure] unstructured [Short display name] Organization Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.1 (P3P1.1) Specification


Input: [Evaluation] Bandwidth efficiency [Picture Element] Yes, requests only what it needs [image-set CSS/uri templates] Yes, requests only what it needs [Request headers] Yes, requests only what it needs [Spacer background-image]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [Picture Element] Yes [image-set CSS/uri templates] Yes [Request headers] Yes [Spacer background-image]

Output: Yes


Input: [Evaluation] Server-side config not required [Picture Element] Client based [image-set CSS/uri templates] Client based [Request headers] Server-config required [Spacer background-image]

Output: Client based


Input: [Evaluation] Structure Simplicity (HTML) [Picture Element] Difficult for beginners [image-set CSS/uri templates] (structure not decided, only focuses on CSS) [Request headers] No changes [Spacer background-image]

Output: Existing elements


Input: [Evaluation] Presentation Simplicity (CSS) [Picture Element] Yes [image-set CSS/uri templates] Difficult for beginners, but consistent image-set for backgrounds [Request headers] No changes [Spacer background-image]

Output: Heavy use of media queries


Input: [Evaluation] Easy of maintenance [Picture Element] Responsive scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Request headers] Server-side config [Spacer background-image]

Output: Control image variants with CSS


Input: [Evaluation] Separation of concerns [Picture Element] Presentation scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Request headers] Depends on implementation [Spacer background-image]

Output: Control image variants with CSS


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [Picture Element] Yes [image-set CSS/uri templates] This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide. [Request headers] No [Spacer background-image]

Output: No


Input: [Evaluation] Centralized image variants [Picture Element] Located within structure [image-set CSS/uri templates] Variants formats within image-set() urls [Request headers] Depends on implementation [Spacer background-image]

Output: Variants within media queries


Input: [Evaluation] Request static images [Picture Element] Yes [image-set CSS/uri templates] Yes [Request headers] Yes [Spacer background-image]

Output: Yes


Input: [Evaluation] Request dynamically resized images [Picture Element] Manually code dimensions within urls [image-set CSS/uri templates] Request exact dimension needed [Request headers] Yes [Spacer background-image]

Output: Manually code dimensions within urls


Input: [Evaluation] High-resolution when the device is capable [Picture Element] Yes, from media queries [image-set CSS/uri templates] Yes, from image-set() [Request headers] Yes, but may be maintained by user agent [Spacer background-image]

Output: Yes, from media queries


Input: [Evaluation] Adjusts to device bandwidth [Picture Element] Yes (if bandwidth added to media queries) [image-set CSS/uri templates] Yes (if bandwidth added to image-set) [Request headers] No [Spacer background-image]

Output: Yes (if bandwidth added to media queries)


Input: [Evaluation] Fallback for browsers without support [Picture Element] Yes, img within noscript [image-set CSS/uri templates] (no structure to evaluate) [Request headers] Yes [Spacer background-image]

Output: Yes


Input: [Evaluation] Printable images [Picture Element] Yes [image-set CSS/uri templates] Yes [Request headers] Yes [Spacer background-image]

Output: No


Input: [Evaluation] Polyfill [Picture Element] Yes [image-set CSS/uri templates] Yes [Request headers] Not needed [Spacer background-image]

Output: Not needed


Input: [Evaluation] Minimal structure updates for browser support [Picture Element] Create a new picture element [image-set CSS/uri templates] (no structure to evaluate) [Request headers] Heavy restructuring [Spacer background-image]

Output: Not needed


Input: [Evaluation] Minimal presentation updates for browser support [Picture Element] No new CSS required [image-set CSS/uri templates] image-set being evaluated by webkit for background images [Request headers] No new CSS required [Spacer background-image]

Output: Not needed


Input: [Evaluation] Image within content [Picture Element] Yes [image-set CSS/uri templates] Yes [Request headers] Yes [Spacer background-image]

Output: No


Input: [Evaluation] No new file formats [Picture Element] Works with existing files [image-set CSS/uri templates] Works with existing files [Request headers] Works with existing files [Spacer background-image]

Output: Works with existing files


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph]

Output: No conflict? Different functionality is to be expected, but do not influence each other

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph]

Output: Conflict; changes through GSP can break consistency in LDPC

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [Event] prepared [Description]

Output: response to prepare indicating that activeGrammars have been successfully prepared

Voice Extensible Markup Language (VoiceXML) 3.0

Table 8: Recognition: Events from Device


Input: [Event] inputStarted [Description]

Output: notification that the onset of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] inputFinished [Description]

Output: notification that the end of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] partialResults [Payload] results (M) [Description]

Output: notification of a partial recognition results

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] recoResults [Payload] results (M) [Description]

Output: notification of final recognition results

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] error [Payload] error status (M) [Description]

Output: an error occurred

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name. [Function]

Output: CreateScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists. [Function]

Output: DeleteScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, value(optional), scopeName(optional) [Return Value] Success or Error [Description] Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope. [Function]

Output: CreateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] Success or Failure [Description] Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope. [Function]

Output: DeleteVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, newValue, scopeName(optional) [Return Value] Success or Failure [Description] Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found. [Function]

Output: UpdateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] value [Description] Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found. [Function]

Output: ReadVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] expr, scopeName(optional) [Return Value] value [Description] Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found. [Function]

Output: EvaluateExpression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [0] UI [.capture*] new non-modal prompt [2] form control derived from input file, part of the page [(resp audio, video)]

Output: new form control, part of the page


Input: [0] scope of new API [.capture*] several new interfaces [2] limited (derive from FileReader) [(resp audio, video)]

Output: limited (derive from FileReader)


Input: [0] In widgets [.capture*] can grant access to API without prompt [2] awkward to use [(resp audio, video)]

Output: awkward to use


Input: [0] Integration with Media gallery [.capture*] left to the developer [2] possibly transparent (but down to the UA) [(resp audio, video)]

Output: possibly transparent (but down to the UA)


Input: [0] viewfinder compat [.capture*] new API calls needed [2] possibly transparent? [(resp audio, video)]

Output: possibly transparent?


Input: [0] control on number and duration of captures [.capture*] available in API [2] number controled by number of fields — awkward user exp; not clear how to control duration [(resp audio, video)]

Output: could be controled with attributes on the input field?


Input: [0] detection for support of capture capabilities [.capture*] possible with boolean flags added to Capture interface [2] not clear; might need flags addition [(resp audio, video)]

Output: not clear either


Input: [0] evolution for more control of the capture devices [.capture*] need new API calls added to Capture [2] no clear path; probably would need API of its own, but not clear how to plug in [(resp audio, video)]

Output: no clear path; probably would need API of its own, but not clear how to plug in


Input: [0] impact/dependence on markup spec (html5?) [.capture*] None [2] Limited [(resp audio, video)]

Output: Not trivial


Input: [Bugzilla bug (if applicable)] Bugzilla bug 16311 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 2 Sequence Normalization 5.1.15 XML Output Method: the item-separator Parameter 6.1.15 XHTML Output Method: the item-separator Parameter 7.4.14 HTML Output Method: the item-separator Parameter 8.1.15 Text Output Method: the item-separator Parameter [Description of change]

Output: Added new serialization parameter for specifying a separator that is inserted between items in the sequence that is to be serialized.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Added XSLT instructions equivalent to XQuery expressions for setting serialization parameters by means of a data model instance, and other editorial corrections and improvements.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Affected sections] 10 Conformance [Description of change]

Output: Clarified the definition of host language to make it clear that APIs can be considered to be host languages.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 6129 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters 5.1.2 XML Output Method: the html-version Parameter 6 XHTML Output Method 6.1.2 XHTML Output Method: the html-version Parameter 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 6.1.7 XHTML Output Method: the doctype-system and doctype-public Parameters 6.1.14 XHTML Output Method: the include-content-type Parameter 7 HTML Output Method 7.1 Markup for Elements 7.2 Writing Attributes 7.3 Writing Character Data 7.4.1 HTML Output Method: the version and html-version Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters D List of URI Attributes [Description of change]

Output: Extended the definitions of the HTML and XHTML output methods to include support for HTML5 serialization.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 17619 [Erratum (if applicable)] None [Category] Editorial [Affected sections] 5.1.1 XML Output Method: the version Parameter 5.1.3 XML Output Method: the encoding Parameter C Summary of Error Conditions [Description of change]

Output: Text associated with links to the definitions of the terms NCName, EncName and VersionNum was repeated several times.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 15915 [Erratum (if applicable)] None [Category] Editorial [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Made uses of the terms "absent" and "unspecified" consistent.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 17282 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters B Schema for Serialization Parameters [Description of change]

Output: Changed type of the normalization-form serialization parameter to NMTOKEN. This would be an incompatible change from XQuery 1.0, for any implementation that supported the Serialization Feature, and supported an implementation-defined value for the normalization-form serialization parameter that did not have the lexical form of an NMToken.

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Evaluation] Bandwidth efficiency [Picture Element] Yes, requests only what it needs [image-set CSS/uri templates] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Server-side config not required [Picture Element] Client based [image-set CSS/uri templates] Client based [Spacer background-image] Client based [Request headers]

Output: Server-config required


Input: [Evaluation] Structure Simplicity (HTML) [Picture Element] Difficult for beginners [image-set CSS/uri templates] (structure not decided, only focuses on CSS) [Spacer background-image] Existing elements [Request headers]

Output: No changes


Input: [Evaluation] Presentation Simplicity (CSS) [Picture Element] Yes [image-set CSS/uri templates] Difficult for beginners, but consistent image-set for backgrounds [Spacer background-image] Heavy use of media queries [Request headers]

Output: No changes


Input: [Evaluation] Easy of maintenance [Picture Element] Responsive scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers]

Output: Server-side config


Input: [Evaluation] Separation of concerns [Picture Element] Presentation scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers]

Output: Depends on implementation


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [Picture Element] Yes [image-set CSS/uri templates] This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide. [Spacer background-image] No [Request headers]

Output: No


Input: [Evaluation] Centralized image variants [Picture Element] Located within structure [image-set CSS/uri templates] Variants formats within image-set() urls [Spacer background-image] Variants within media queries [Request headers]

Output: Depends on implementation


Input: [Evaluation] Request static images [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Request dynamically resized images [Picture Element] Manually code dimensions within urls [image-set CSS/uri templates] Request exact dimension needed [Spacer background-image] Manually code dimensions within urls [Request headers]

Output: Yes


Input: [Evaluation] High-resolution when the device is capable [Picture Element] Yes, from media queries [image-set CSS/uri templates] Yes, from image-set() [Spacer background-image] Yes, from media queries [Request headers]

Output: Yes, but may be maintained by user agent


Input: [Evaluation] Adjusts to device bandwidth [Picture Element] Yes (if bandwidth added to media queries) [image-set CSS/uri templates] Yes (if bandwidth added to image-set) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers]

Output: No


Input: [Evaluation] Fallback for browsers without support [Picture Element] Yes, img within noscript [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Printable images [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers]

Output: Yes


Input: [Evaluation] Polyfill [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Not needed [Request headers]

Output: Not needed


Input: [Evaluation] Minimal structure updates for browser support [Picture Element] Create a new picture element [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Not needed [Request headers]

Output: Heavy restructuring


Input: [Evaluation] Minimal presentation updates for browser support [Picture Element] No new CSS required [image-set CSS/uri templates] image-set being evaluated by webkit for background images [Spacer background-image] Not needed [Request headers]

Output: No new CSS required


Input: [Evaluation] Image within content [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers]

Output: Yes


Input: [Evaluation] No new file formats [Picture Element] Works with existing files [image-set CSS/uri templates] Works with existing files [Spacer background-image] Works with existing files [Request headers]

Output: Works with existing files


Input: [Bugzilla bug (if applicable)] Bugzilla bug 16311 [Erratum (if applicable)] None [Description of change] Added new serialization parameter for specifying a separator that is inserted between items in the sequence that is to be serialized. [Affected sections] 2 Sequence Normalization 5.1.15 XML Output Method: the item-separator Parameter 6.1.15 XHTML Output Method: the item-separator Parameter 7.4.14 HTML Output Method: the item-separator Parameter 8.1.15 Text Output Method: the item-separator Parameter [Category]

Output: Substantive

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Description of change] Added XSLT instructions equivalent to XQuery expressions for setting serialization parameters by means of a data model instance, and other editorial corrections and improvements. [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Category]

Output: Editorial

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Description of change] Clarified the definition of host language to make it clear that APIs can be considered to be host languages. [Affected sections] 10 Conformance [Category]

Output: Editorial

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 6129 [Erratum (if applicable)] None [Description of change] Extended the definitions of the HTML and XHTML output methods to include support for HTML5 serialization. [Affected sections] 3 Serialization Parameters 5.1.2 XML Output Method: the html-version Parameter 6 XHTML Output Method 6.1.2 XHTML Output Method: the html-version Parameter 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 6.1.7 XHTML Output Method: the doctype-system and doctype-public Parameters 6.1.14 XHTML Output Method: the include-content-type Parameter 7 HTML Output Method 7.1 Markup for Elements 7.2 Writing Attributes 7.3 Writing Character Data 7.4.1 HTML Output Method: the version and html-version Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters D List of URI Attributes [Category]

Output: Substantive

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 17619 [Erratum (if applicable)] None [Description of change] Text associated with links to the definitions of the terms NCName, EncName and VersionNum was repeated several times. [Affected sections] 5.1.1 XML Output Method: the version Parameter 5.1.3 XML Output Method: the encoding Parameter C Summary of Error Conditions [Category]

Output: Editorial

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 15915 [Erratum (if applicable)] None [Description of change] Made uses of the terms "absent" and "unspecified" consistent. [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Category]

Output: Editorial

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [Bugzilla bug (if applicable)] Bugzilla 17282 [Erratum (if applicable)] None [Description of change] Changed type of the normalization-form serialization parameter to NMTOKEN. This would be an incompatible change from XQuery 1.0, for any implementation that supported the Serialization Feature, and supported an implementation-defined value for the normalization-form serialization parameter that did not have the lexical form of an NMToken. [Affected sections] 3 Serialization Parameters B Schema for Serialization Parameters [Category]

Output: Substantive

XSLT and XQuery Serialization 3.0 -- Review Version


Input: [0] UI [.capture*] new non-modal prompt [(resp audio, video)] new form control, part of the page [2]

Output: form control derived from input file, part of the page


Input: [0] scope of new API [.capture*] several new interfaces [(resp audio, video)] limited (derive from FileReader) [2]

Output: limited (derive from FileReader)


Input: [0] In widgets [.capture*] can grant access to API without prompt [(resp audio, video)] awkward to use [2]

Output: awkward to use


Input: [0] Integration with Media gallery [.capture*] left to the developer [(resp audio, video)] possibly transparent (but down to the UA) [2]

Output: possibly transparent (but down to the UA)


Input: [0] viewfinder compat [.capture*] new API calls needed [(resp audio, video)] possibly transparent? [2]

Output: possibly transparent?


Input: [0] control on number and duration of captures [.capture*] available in API [(resp audio, video)] could be controled with attributes on the input field? [2]

Output: number controled by number of fields — awkward user exp; not clear how to control duration


Input: [0] detection for support of capture capabilities [.capture*] possible with boolean flags added to Capture interface [(resp audio, video)] not clear either [2]

Output: not clear; might need flags addition


Input: [0] evolution for more control of the capture devices [.capture*] need new API calls added to Capture [(resp audio, video)] no clear path; probably would need API of its own, but not clear how to plug in [2]

Output: no clear path; probably would need API of its own, but not clear how to plug in


Input: [0] impact/dependence on markup spec (html5?) [.capture*] None [(resp audio, video)] Not trivial [2]

Output: Limited


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Collection = GSP endpoint] Conflict [LDP Collection = GSP graph]

Output: No conflict? Different functionality is to be expected, but do not influence each other

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Collection = GSP endpoint] No conflict [LDP Collection = GSP graph]

Output: Conflict; changes through GSP can break consistency in LDPC

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Expected Values] alternativeText Visual [Description] alternative text is provided for visual content (e.g., the HTML alt attribute). [Augmented Access Mode]

Output: Textual


Input: [Expected Values] longDescription Visual [Description] descriptions are provided for image-based visual content and/or complex structures such as tables, mathematics, diagrams or charts. [Augmented Access Mode]

Output: Textual


Input: [Expected Values] ChemML laTex MathML Visual [Description] The use of one of these specific ASCII/XML encodings for mathematics or chemistry. These can have extensions specified, but are rarely needed. [Augmented Access Mode]

Output: Textual


Input: [Expected Values] transcript Auditory [Description] The addition of a separate transcript to convey the meaning of the audio. [Augmented Access Mode]

Output: Textual


Input: [Expected Values] captions Auditory [Description] The addition of synchronized text (closed captions) to convey the meaning of the audio. Note that while many captions may be implemented as textual in the transport, users think of them as being a visual appearance. [Augmented Access Mode]

Output: Visual


Input: [Expected Values] signLanguage Auditory [Description] The presentation of audio in sign language in the visual presentation. The most likely extension is /sgn-en-us or other ISO 639 sign language code. [Augmented Access Mode]

Output: Visual


Input: [Expected Values] audioDescription Visual [Description] Audio descriptions are available (e.g., via the HTML5 track element). Common extensions are for the various "onImage" refinements noted above. [Augmented Access Mode]

Output: Auditory


Input: [Expected Values] braille Visual or Textual [Description] braille content or alternative is available (e.g., eBraille or print braille) This can have extensions for the different types of braille, /ASCII, /music, /math, /chem or /nemeth) (also consider /contracted and /gradeII or other nomenclature... pretty open) [Augmented Access Mode]

Output: Tactile


Input: [Expected Values] tactileGraphic Visual [Description] tactile graphics have been provided, as described in the BANA Guidelines and Standards for Tactile Graphics. [Augmented Access Mode]

Output: Tactile


Input: [Expected Values] tactileObject Visual [Description] tactile 3D objects have been defined and a 3D object or instructions to build one are available. [Augmented Access Mode]

Output: Tactile


Input: [Type] DOMString[] [Nullable] ✘ [Optional] ✘ [Description] This argument identifies an array containing the properties for which the values need to be retrieved. For an empty array all properties carrying values will be retrieved. Optional arguments allow refining the request. [Parameter]

Output: propertyNames


Input: [Type] PropertyCallback [Nullable] ✘ [Optional] ✘ [Description] This argument holds a callback object for asynchronous requests to the property. The successCallback object implements the PropertyCallback interface and holds a handleEvent operation that needs to be called once all data for the requested property is gathered. This handleEvent operation needs to be called with a new MediaAnnotation array. [Parameter]

Output: successCallback


Input: [Type] ErrorCallback [Nullable] ✘ [Optional] ✘ [Description] This argument holds a callback object for failure of asynchronous requests to the property. The errorCallback object implements the ErrorCallback interface and holds a handleEvent operation that needs to be called if an attempt fails. This handleEvent operation needs to be called with a new DOMString representing the status code of the error (see Section 4.7 for details). [Parameter]

Output: errorCallback


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument contains a URI identifying the specific media fragment for which the metadata is requested. The URI must conform to the URI for Media Fragment [MEDIA-FRAGMENTS] specification. This parameter is optional. [Parameter]

Output: fragment


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument identifies a specific metadata format. It should use the metadata format identifiers defined in the Ontology for Media Resources 1.0 specification [MEDIA-ONTOLOGY]. If a metadata format is defined, only the metadata available in the corresponding metadata format are retrieved. This parameter is optional. [Parameter]

Output: sourceFormat


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument allows to identify the language of the metadata. Values for the metadata will only be returned if it is available in the specified language. Recommended best practice is to use BCP 47 [BCP47]. This parameter is optional. [Parameter]

Output: language


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: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.