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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Erratum] E1 [Bugzilla] 4372 [Description] This erratum places constraints on the type of string that is valid for the doctype-public attribute of xsl:output. [Category]

Output: substantive


Input: [Erratum] E2 [Bugzilla] 4557 [Description] This erratum corrects an editorial error concerning the number of phases of serialization. [Category]

Output: editorial


Input: [Erratum] E3 [Bugzilla] 5066 [Description] This erratum corrects an editorial error concerning the currently registered XHTML media types. [Category]

Output: editorial


Input: [Erratum] E4 [Bugzilla] 5433 [Description] This erratum clarifies how descendant elements of an XML island must be serialized according to the HTML output method. [Category]

Output: substantive


Input: [Erratum] E5 [Bugzilla] 5439 [Description] This erratum aligns the description of the effect of the include-content-type serialization parameter of the HTML output method with that of the XHTML output method. [Category]

Output: substantive


Input: [Erratum] E6 [Bugzilla] 5458 [Description] This erratum ensures that the sequence normalization process preserves any type annotations associated with nodes in the input sequence. [Category]

Output: substantive


Input: [Erratum] E7 [Bugzilla] 5300 [Description] This erratum clarifies how elements with empty content models are to be serialized under the HTML and XHTML output methods. [Category]

Output: substantive


Input: [Erratum] E8 [Bugzilla] 5441 [Description] This erratum ensures that Unicode normalization applies to all characters that might be adjacent in the serialized result produced by the text output method, including those that are in text nodes that are separated by element nodes in the data model instance. [Category]

Output: substantive


Input: [Erratum] E9 [Bugzilla] 5993 [Description] This erratum makes previously non-normative text that describes how the xhtml and html output methods must behave if the indent parameter has the value yes into normative text. [Category]

Output: substantive


Input: [Erratum] E10 [Bugzilla] 6466 [Description] This erratum specifies the syntactic constraints on the values of the doctype-public and doctype-system serialization parameters. [Category]

Output: substantive


Input: [Erratum] E11 [Bugzilla] 6376 [Description] This erratum makes clear which parts of the recommendation are not considered to be normative. [Category]

Output: editorial


Input: [XKMS element.attribute name] MessageAbstractType.Service [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Signature [Required]

Output: Optional, may be used to support non-repudiation for both Request and Response messages

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] ResultType.RequestId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] PendingRequestType.ResponseId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Nonce [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.RespondWith=Represent [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] Request/MessageHash [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Alarm API [Source] SysApps Charter [Description]

Output: Applications can create alarms, notifying users

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Contacts API [Source] SysApps Charter [Description]

Output: Apps can add, remove and edit contacts

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Messaging API [Source] SysApps Charter [Description]

Output: Apps can send, receive and view SMS

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Telephony API [Source] SysApps Charter [Description]

Output: Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Raw Sockets API [Source] SysApps Charter [Description]

Output: Apps can create, manipulate and listen for low-level TCP and UDP connections

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Supports many device form factors [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Description]

Output: Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] DAP API Support [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Description]

Output: All APIs defined by DAP should be accessible to system applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Minimal user prompting [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Description]

Output: Problems such as 'double prompting' should be avoided when integrating other APIs

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] HTML5 [Description]

Output: Applications consist of HTML, CSS and JavaScript

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Location [Description]

Output: Applications have access to geolocation data

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with other applications [Implications] Some kind of messaging will be supported [Description]

Output: Applications can communicate with other applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Implications] Access remote domains will be possible [Description]

Output: Applications can communicate with pre-defined web addresses

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Valid across multiple platforms [Source] Compatibility of application packages [Description]

Output: Applications can run on any conformant platform, potentially including any device form factor

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Access control log [Source] webinos [Description]

Output: Allow access control decisions to be logged.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] API access rationale [Source] webinos [Description]

Output: Applications shall be able to explain why access to data or APIs is being requested.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application capability restriction [Source] webinos [Description]

Output: Applications shall access only its specified device features, extensions and content.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application intent [Source] webinos [Description]

Output: Applications shall specify its required functionality at install time or during updates.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application isolation [Source] webinos [Description]

Output: Applications shall be isolated from each other.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Application policy approval [Source] webinos [Description]

Output: Changes to existing application intentions and permissions shall be approved by the end user.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Authenticity check [Source] webinos [Description]

Output: Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Certifier list [Source] webinos [Description]

Output: The list of authorities that certified an application shall be viewable by end-users.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Confidential credentials storage [Source] webinos [Description]

Output: The webinos runtime shall support the confidential storage of user credentials.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Credentials access restriction [Source] webinos [Description]

Output: Access to credentials storage shall be limited to a specific user, a specific device and a set of applications.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Data management rationale [Source] webinos [Description]

Output: applications shall be able to explain how collected sensitive data will be managed.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Default policy [Source] webinos [Description]

Output: A default security and privacy policy shall exist an be enforced on each conformant runtime

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Device-identity binding [Source] webinos [Description]

Output: Personal devices shall be bound to their owner's identities.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Device-identity binding revokation [Source] webinos [Description]

Output: The binding between personal devices and owner's identity shall be revokable.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Hierarchical policy enforcement [Source] webinos [Description]

Output: Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Secure cache [Source] webinos [Description]

Output: Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Secure storage [Source] webinos [Description]

Output: Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Trusted application source [Source] webinos [Implications] Apps must have provenance data attached to them [Description]

Output: When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App stores can revoke applications [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Description]

Output: "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app"

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] The user is not the only source of access control decisions. this also suggests a need for conflict resolution. [Description]

Output: B2G: "App store must be able to set the default permissions for an app".

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Installation [Source] B2G, webinos [Description]

Output: Applications must be installed before executed

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Owner override [Source] B2G (user), webinos (user) [Implications] Access control settings must be changeable [Description]

Output: The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example)

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] App privilege visibility [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] There must be a standard way for applications to identify the permissions they have and lack [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Permission usability [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Non-browser security context: may be additional restrictions on HTML/JavaScript [Description]

Output: Apps should not be vulnerable to common web vulnerabilities when granted significant privileges

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Different 'levels' apply to SysApps - possibly 'roles' [Description]

Output: Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Access to files outside owned by the platform [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications] Need to provide both sandboxed and non-sandboxed storage [Description]

Output: Ability for a system application to access (read and write) files outside of that application's sandboxed storage area.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [Default Action] Initiate the drag-and-drop operation [dropEffect]

Output: "none"


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Continue the drag-and-drop operation [dropEffect]

Output: "none"


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] dragleave [Target] Previous target element [Cancelable?] — [Drag data store mode] Protected mode [Default Action] None [dropEffect]

Output: "none"


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [Drag data store mode] Protected mode [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Property]

Output: Properties from Place[2]

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


Input: [Expected Type] PostalAddress [Description] Physical address of the item. [Property]

Output: address

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


Input: [Expected Type] aggregateRating [Description] The overall rating, based on a collection of reviews or ratings, of the item. [Property]

Output: aggregateRating

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


Input: [Expected Type] GeoCoordinates or GeoShape [Description] The geo coordinates of the place. [Property]

Output: geo

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


Input: [Expected Type] URL [Description] A URL to a map of the place. [Property]

Output: map

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


Input: [Expected Type] ImageObject or Photograph [Description] Photographs of this place [Property]

Output: photos

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


Input: [Expected Type] Review [Description] Review of the item [Property]

Output: reviews

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


Input: [Expected Type] Text [Description] The telephone number. [Property]

Output: telephone

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


Input: [Erratum] E1 [Bugzilla] 4372 [Category] substantive [Description]

Output: This erratum places constraints on the type of string that is valid for the doctype-public attribute of xsl:output.


Input: [Erratum] E2 [Bugzilla] 4557 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the number of phases of serialization.


Input: [Erratum] E3 [Bugzilla] 5066 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the currently registered XHTML media types.


Input: [Erratum] E4 [Bugzilla] 5433 [Category] substantive [Description]

Output: This erratum clarifies how descendant elements of an XML island must be serialized according to the HTML output method.


Input: [Erratum] E5 [Bugzilla] 5439 [Category] substantive [Description]

Output: This erratum aligns the description of the effect of the include-content-type serialization parameter of the HTML output method with that of the XHTML output method.


Input: [Erratum] E6 [Bugzilla] 5458 [Category] substantive [Description]

Output: This erratum ensures that the sequence normalization process preserves any type annotations associated with nodes in the input sequence.


Input: [Erratum] E7 [Bugzilla] 5300 [Category] substantive [Description]

Output: This erratum clarifies how elements with empty content models are to be serialized under the HTML and XHTML output methods.


Input: [Erratum] E8 [Bugzilla] 5441 [Category] substantive [Description]

Output: This erratum ensures that Unicode normalization applies to all characters that might be adjacent in the serialized result produced by the text output method, including those that are in text nodes that are separated by element nodes in the data model instance.


Input: [Erratum] E9 [Bugzilla] 5993 [Category] substantive [Description]

Output: This erratum makes previously non-normative text that describes how the xhtml and html output methods must behave if the indent parameter has the value yes into normative text.


Input: [Erratum] E10 [Bugzilla] 6466 [Category] substantive [Description]

Output: This erratum specifies the syntactic constraints on the values of the doctype-public and doctype-system serialization parameters.


Input: [Erratum] E11 [Bugzilla] 6376 [Category] editorial [Description]

Output: This erratum makes clear which parts of the recommendation are not considered to be normative.


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Authentication mechanism defined by TLS which clients must implement

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Not required

XML Key Management Specification (XKMS 2.0) Bindings


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

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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


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

Output: Text field


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

Output: Search field


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

Output: A text field


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

Output: A text field


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

Output: A text field


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

Output: Text field that obscures data entry


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

Output: A date and time control


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

Output: A date control


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

Output: A month control


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

Output: A week control


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

Output: A time control


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

Output: A date and time control


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

Output: A text field or spinner control


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

Output: A slider control or similar


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

Output: A color well


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

Output: A checkbox


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

Output: A radio button


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

Output: A label and a button


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

Output: A button


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

Output: Either a clickable image, or a button


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

Output: A button


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

Output: A button


Input: [0] The cells in [1] this table [2]

Output: should go


Input: [0] green when [1] you hover [2]

Output: the pointing


Input: [0] The rows in [1] this table [2]

Output: should go


Input: [0] dark green [1] when the [2]

Output: pointing device


Input: [0] is over the [1] five pixel [2]

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


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: [Description] Applications can create alarms, notifying users [Source] SysApps Charter [Requirement]

Output: Alarm API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can add, remove and edit contacts [Source] SysApps Charter [Requirement]

Output: Contacts API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can send, receive and view SMS [Source] SysApps Charter [Requirement]

Output: Messaging API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log [Source] SysApps Charter [Requirement]

Output: Telephony API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can create, manipulate and listen for low-level TCP and UDP connections [Source] SysApps Charter [Requirement]

Output: Raw Sockets API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Requirement]

Output: Supports many device form factors

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] All APIs defined by DAP should be accessible to system applications [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Requirement]

Output: DAP API Support

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Problems such as 'double prompting' should be avoided when integrating other APIs [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Requirement]

Output: Minimal user prompting

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications consist of HTML, CSS and JavaScript [Requirement]

Output: HTML5

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications have access to geolocation data [Requirement]

Output: Location

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can communicate with other applications [Implications] Some kind of messaging will be supported [Requirement]

Output: Communicate with other applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can communicate with pre-defined web addresses [Implications] Access remote domains will be possible [Requirement]

Output: Communicate with pre-defined endpoints

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can run on any conformant platform, potentially including any device form factor [Source] Compatibility of application packages [Requirement]

Output: Valid across multiple platforms

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Allow access control decisions to be logged. [Source] webinos [Requirement]

Output: Access control log

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall be able to explain why access to data or APIs is being requested. [Source] webinos [Requirement]

Output: API access rationale

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall access only its specified device features, extensions and content. [Source] webinos [Requirement]

Output: Application capability restriction

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall specify its required functionality at install time or during updates. [Source] webinos [Requirement]

Output: Application intent

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall be isolated from each other. [Source] webinos [Requirement]

Output: Application isolation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Changes to existing application intentions and permissions shall be approved by the end user. [Source] webinos [Requirement]

Output: Application policy approval

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime [Source] webinos [Requirement]

Output: Authenticity check

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The list of authorities that certified an application shall be viewable by end-users. [Source] webinos [Requirement]

Output: Certifier list

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The webinos runtime shall support the confidential storage of user credentials. [Source] webinos [Requirement]

Output: Confidential credentials storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Access to credentials storage shall be limited to a specific user, a specific device and a set of applications. [Source] webinos [Requirement]

Output: Credentials access restriction

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] applications shall be able to explain how collected sensitive data will be managed. [Source] webinos [Requirement]

Output: Data management rationale

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] A default security and privacy policy shall exist an be enforced on each conformant runtime [Source] webinos [Requirement]

Output: Default policy

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Personal devices shall be bound to their owner's identities. [Source] webinos [Requirement]

Output: Device-identity binding

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The binding between personal devices and owner's identity shall be revokable. [Source] webinos [Requirement]

Output: Device-identity binding revokation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy. [Source] webinos [Requirement]

Output: Hierarchical policy enforcement

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites. [Source] webinos [Requirement]

Output: Secure cache

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities. [Source] webinos [Requirement]

Output: Secure storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Trusted application source

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: App stores can revoke applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: External trusted party can set app default permissions

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Installation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Owner override

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: App privilege visibility

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Permission usability

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Immunity to browser-based threats

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Pre-installed app permissions

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Access to files outside owned by the platform

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Probably a layout table


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

Output: Probably a layout table


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

Output: Probably a layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

Output: Probably a non-layout table


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

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


Input: [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: [Requirement] Supports many device form factors [Description] Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices [Source] SysApps Charter [Implications]

Output: The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] DAP API Support [Description] All APIs defined by DAP should be accessible to system applications [Source] SysApps Charter [Implications]

Output: Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Minimal user prompting [Description] Problems such as 'double prompting' should be avoided when integrating other APIs [Source] SysApps Charter [Implications]

Output: Some details of the expected user interactions may need to be specified in the security model or APIs

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with other applications [Description] Applications can communicate with other applications [Implications]

Output: Some kind of messaging will be supported

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Description] Applications can communicate with pre-defined web addresses [Implications]

Output: Access remote domains will be possible

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Trusted application source [Description] When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application. [Source] webinos [Implications]

Output: Apps must have provenance data attached to them

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: App permissions can be changed remotely

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Description] B2G: "App store must be able to set the default permissions for an app". [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: The user is not the only source of access control decisions. this also suggests a need for conflict resolution.

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Access control settings must be changeable

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: There must be a standard way for applications to identify the permissions they have and lack

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Description] Apps should not be vulnerable to common web vulnerabilities when granted significant privileges [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Non-browser security context: may be additional restrictions on HTML/JavaScript

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Description] Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Different 'levels' apply to SysApps - possibly 'roles'

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


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

Output: Need to provide both sandboxed and non-sandboxed storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Checkpoint] 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) [Comments]

Output: PDF provides support for language identification for documents. The ISO 32000-1 PDF Specification details language support in section 14.9.2. Test results: Test id 16 (document with non-English default language)

Accessibility Support Documentation for PDF

Guideline 3.1 Readable: Make text content readable and understandable


Input: [Checkpoint] 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) [Comments]

Output: PDF provides support for language identification for parts of documents. Test results: Test id 17 (Document with English primary language which includes Spanish phrases)

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA) [Comments]

Output: No Accessibility Support impact. PDF document authors can provide a link to a definition of unusual words or phrases.

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA) [Comments]

Output: PDF document authors can provide an explanation for abbreviations either by providing the expanded form immediately following the first instance of the abbreviation, by linking to a definition of the abbreviation, or by providing expansion text as a text equivalent to the abbreviation text. PDF supports abbreviations in tagged PDF by using a span and an abbreviation property. The ISO 32000-1 PDF Specification details abbreviation support in section 14.9.5. Test results: Test id 18 (Markup abbreviations in PDF tags)

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA) [Comments]

Output: No Accessibility Support impact. This is design-specific. Application or document authors need to consider this provision and ensure conformance.

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA) [Comments]

Output: PDF documents support this success criteria when document authors provide pronunciation information using general techniques: G120: Providing the pronunciation immediately following the word G121: Linking to pronunciations G62: Providing a glossary

Accessibility Support Documentation for PDF


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


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

Output: Date and Time


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

Output: Date


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

Output: Month


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

Output: Week


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

Output: Time


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

Output: Local Date and Time


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

Output: Number


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

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


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

Output: File Upload


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

Output: Submit Button


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

Output: Image Button


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

Output: Reset Button


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

Output: Button


Input: [Field Name] name [Details]

Output: 'dialog.user.*'

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] dialogid [Details]

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connectionid [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] conferenceid [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] namelist [Details]

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

Voice Browser Call Control: CCXML Version 1.0


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

Output: Values associated with the event.

Voice Browser Call Control: CCXML Version 1.0


Input: [0] scheme [case] insensitive [match]

Output: exact


Input: [0] userInfo [case] sensitive [match]

Output: exact


Input: [0] host [case] insensitive [match]

Output: endswith


Input: [0] port [case] sensitive [match]

Output: exact


Input: [0] path [case] sensitive [match]

Output: startswith


Input: [0] query [case] sensitive [match]

Output: startswith


Input: [0] fragment [case] sensitive [match]

Output: startswith


Input: [0] uri [case] sensitive [match]

Output: regex


Input: SMS MMS mobile web voice service [Criteria]

Output: Category

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Type of services provided infrastructure type of tools e.g. sms hub, voice platform task specific e.g. market prices type of tool authoring tools e.g. CMS, html auhtoring tool [Criteria]

Output: Type of service

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: healthcare education agriculture government [Criteria]

Output: Sector

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Notes] Addition of this field was recommended at the meeting on the 23rd to augment the 'sector' category. This could be a standalone value or, a sub-value to the chosen value in Sector (i.e. choose 'healthcare' then, choose use cases specific to healthcare) [Criteria]

Output: Use case

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: voice (voice XML, other voice) signaling (SMS, USSD) data connection (mobile web, other data) [Criteria]

Output: Transport layer

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: What is the cost structure? none one-off cost subscription Are there associated tools or components required? software e.g. certain type of server and libraries hardware e.g. a Mac, Linux network capability e.g. 3G, Brew operator specific capability [Criteria]

Output: Initial cost of tool

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: electricity e.g. computers, servers running 24 hrs a day internet access (what speed?) hosting [Criteria]

Output: Long-term costs and infrastructure

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: does it need authorization and partnerships with operators? does it work accross multiple operators? does it work across multiple networks standards? [Criteria]

Output: Operator independence

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Is the tool (or aspects of it) open source? Are there license restrictions? [Criteria]

Output: License

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Time required to learn, set up, and deploy the tool [Notes] e.g. days, weeks, months [Criteria]

Output: Deployment time

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Are plug-ins or additional components available? Are new features planned? Is the tool relatively future-proof from a technology point of view? [Criteria]

Output: Roadmap

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: How many existing users/deployments? Are there case studies available? [Criteria]

Output: Existing user base

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: technology skills programming languages other skills to operate or deploy the tool. [Criteria]

Output: Required skills for deployment

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Resources required to maintain the tool or service. frequency of maintenance frequency of software updates (if provided by the tool creator) skills required for updates or maintenance e.g. does this require a specialist? time e.g. wordpress updates are provided by the creators however each update requires time to install, adjust settings, verify nothing has broken etc. [Criteria]

Output: Maintenance

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Is documentation available? Is it comprehensive? It is multilingual? Is it online or offline? Who is the target audience? e.g. end-users vs those who deploy the tool [Criteria]

Output: Documentation

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: Is additional content required for this tool to function effectively? [Notes] Trying to capture external costs that might be related to the tool. An example might be, an open source server that sends SMS updates, but would require some 3rd party (e.g. health practitioners) to create the SMS content at regular intervals. [Criteria]

Output: Content requirements

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: What audience can be served using this tool? age region (if relevant) spoken language literacy level (language, numeracy, technology) [Criteria]

Output: Audience

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Event Name] dragstart [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] drag [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] Continue the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] dragenter [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Target]

Output: Immediate user selection or the body element


Input: [Event Name] dragleave [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] None [Target]

Output: Previous target element


Input: [Event Name] dragover [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Target]

Output: Current target element


Input: [Event Name] drop [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Current target element


Input: [Event Name] dragend [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Source node


Input: [WSC Clause] I [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] II [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] IIa [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] IV [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] V [Opera] Conforms Optional [Chrome] Does Not Conform Optional [Firefox]

Output: Does Not Conform Optional


Input: [WSC Clause] VI [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] VII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] VIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] IX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] X [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XIII [Opera] Conforms Optional [Chrome] Does Not Conform Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XV [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XVII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XIX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XX [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XXI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXIII [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] XXIV [Opera] Conforms Optional [Chrome] Does Not Conform Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XXV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXVII [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] XXVIII [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] XXIX [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] XXX [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] XXXI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXVII [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XXXVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XXXIX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XL [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLI [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] XLII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLVII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XLIX [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] L [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LI [Opera] Does Not Conform Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LII [Opera] Does Not Conform Advanced [Chrome] Does Not Conform Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LIII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LIV [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LV [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LVI [Opera] Does Not Conform Optional [Chrome] Conforms Optional [Firefox]

Output: Does Not Conform Optional


Input: [WSC Clause] LVII [Opera] Does Not Conform Optional [Chrome] Does Not Conform Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] LVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LIX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LX [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXIII [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LXIV [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LXV [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXVII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXVIII [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] LXIX [Opera] Conforms Optional [Chrome] Does Not Conform Optional [Firefox]

Output: Does Not Conform Optional


Input: [WSC Clause] LXX [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXIII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXIV [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXV [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LXXVI [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LXXVII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXIX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXX [Opera] Does Not Conform Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXXI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXXII [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] LXXXIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXXIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXXV [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] LXXXVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXXVII [Opera] Conforms Optional [Chrome] Conforms Optional [Firefox]

Output: Conforms Optional


Input: [WSC Clause] LXXXVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] LXXXIX [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] XC [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] XCIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCVI [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCVII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCVIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] XCIX [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] C [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] CI [Opera] NA [Chrome] NA [Firefox]


Input: [WSC Clause] CII [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] CIII [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] CIV [Opera] Conforms Basic [Chrome] Conforms Basic [Firefox]

Output: Conforms Basic


Input: [WSC Clause] CV [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [WSC Clause] CVI [Opera] Conforms Advanced [Chrome] Conforms Advanced [Firefox]

Output: Conforms Advanced


Input: [Name] string-set [Value] [[ ] [, ]* ] | none [Initial] none [Applies to] all elements, but not pseudo-elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: all

CSS Generated Content for Paged Media Module


Input: [Name] running [Initial] none [Applies to] elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: all

CSS Generated Content for Paged Media Module


Input: [Name] footnote-display [Value] block | inline | compact [Initial] block [Applies to] elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: paged

CSS Generated Content for Paged Media Module


Input: [Name] footnote-policy [Value] auto | line | block [Initial] auto [Applies to] elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: paged

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-level [Value] none | [Initial] none [Applies to] all elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: paged

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-label [Value] | none [Initial] none [Applies to] all elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: paged

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-state [Value] open | closed [Initial] open [Applies to] block-level elements [Inh.] no [%ages] N/A [Computed value] specified value [Media]

Output: paged

CSS Generated Content for Paged Media Module


Input: [Name] string-set [Value] [[ ] [, ]* ] | none [Applies to] all elements, but not pseudo-elements [Inh.] no [%ages] N/A [Media] all [Computed value] specified value [Initial]

CSS Generated Content for Paged Media Module


Input: [Name] running [Applies to] elements [Inh.] no [%ages] N/A [Media] all [Computed value] specified value [Initial]

CSS Generated Content for Paged Media Module


Input: [Name] footnote-display [Value] block | inline | compact [Applies to] elements [Inh.] no [%ages] N/A [Media] paged [Computed value] specified value [Initial]

Output: block

CSS Generated Content for Paged Media Module


Input: [Name] footnote-policy [Value] auto | line | block [Applies to] elements [Inh.] no [%ages] N/A [Media] paged [Computed value] specified value [Initial]

Output: auto

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-level [Value] none | [Applies to] all elements [Inh.] no [%ages] N/A [Media] paged [Computed value] specified value [Initial]

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-label [Value] | none [Applies to] all elements [Inh.] no [%ages] N/A [Media] paged [Computed value] specified value [Initial]

CSS Generated Content for Paged Media Module


Input: [Name] bookmark-state [Value] open | closed [Applies to] block-level elements [Inh.] no [%ages] N/A [Media] paged [Computed value] specified value [Initial]

Output: open

CSS Generated Content for Paged Media Module


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

Output: No conflict

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 Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

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 Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

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 Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict

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 Container = GSP endpoint] Conflict [LDP Container = GSP graph]

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

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 Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: No conflict

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 Container = GSP endpoint] No conflict [LDP Container = GSP graph]

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

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


Input: [Property] namespace name [EXI event types]

Output: AT

Mapping of the attribute information item properties to EXI event types


Input: [Property] local name [EXI event types]

Output: AT


Input: [Property] prefix [EXI event types]

Output: AT


Input: [Property] normalized value [EXI event types]

Output: The value of AT


Input: [Property] specified [EXI event types]

Output: True if the item maps to AT, otherwise false


Input: [Property] attribute type [EXI event types]

Output: Computed based on AT and DT


Input: [Property] references [EXI event types]

Output: Computed based on attribute type and value of AT


Input: [Property] owner element [EXI event types]

Output: Computed based on the last SE event encountered that did not get a matching EE event


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] recognized as XML, parsing failed [text/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] type 1 error occured, browser crashed [text/xml]

Output: type 1 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] type 1 error occured, browser crashed [text/xml]

Output: type 1 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not checked [application/xhtml+xml] not supported [application/xml] failed correctly [text/xml]

Output: failed correctly

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] not supported [application/xml] failed correctly while parsing the DTD [text/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Microsoft Internet Explorer 5.1.4/Mac


Input: [Component] FTCaseOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be case insensitive or case sensitive. [Default initial value]

Output: case insensitive

Static Context Components


Input: [Component] FTDiacriticsOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be diacritics insensitive or diacritics sensitive. [Default initial value]

Output: diacritics insensitive

Static Context Components


Input: [Component] FTStemOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without stemming or with stemming. [Default initial value]

Output: without stemming

Static Context Components


Input: [Component] FTThesaurusOption overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known thesauri. [Default initial value]

Output: without thesaurus

Static Context Components


Input: [Component] Statically known thesauri augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a thesaurus list. [Default initial value]

Static Context Components


Input: [Component] FTStopWordOption overwriteable overwriteable by prolog (refer to default to augment) [Scope] lexical [Consistency rules] Value must be part of the statically known stop word lists. [Default initial value]

Output: without stopwords

Static Context Components


Input: [Component] Statically known stop word lists augmentable cannot be augmented or overwritten by prolog [Scope] module [Consistency rules] Each URI uniquely identifies a stop word list. [Default initial value]

Static Context Components


Input: [Component] FTLanguageOption overwriteable overwriteable by prolog [Scope] lexical [Consistency rules] Value must be castable to "xs:language" or "none". [Default initial value]

Output: no language is selected

Static Context Components


Input: [Component] FTWildCardOption no overwriteable by prolog [Scope] lexical [Consistency rules] Value must be without wildcards or without wildcards. [Default initial value]

Output: without wildcards

Static Context Components


Input: [Name] alignment-baseline [Values] auto | baseline | before-edge | text-before-edge | middle | central | after-edge | text-after-edge | ideographic | alphabetic | hanging | mathematical [Applies to] ‘tspan’, ‘textPath’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: see property description


Input: [Name] baseline-shift [Values] baseline | sub | super | | [Applies to] ‘tspan’, ‘textPath’ elements [Inh.] no [Percentages] refer to the "line height" of the ‘text’ element, which in the case of SVG is defined to be equal to the font size [Media] visual [Anim.] yes [Initial value]

Output: baseline


Input: [Name] buffered-rendering [Values] auto | dynamic | static [Applies to] container elements and graphics elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] clip [Values] | auto [Applies to] elements which establish a new viewport, ‘pattern’ elements and ‘marker’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] clip-path [Values] | | none [Applies to] container elements and graphics elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]


Input: [Name] clip-rule [Values] nonzero | evenodd [Applies to] graphics elements within a ‘clipPath’ element [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: nonzero


Input: [Name] color [Applies to] elements to which properties ‘fill’, ‘stroke’, ‘stop-color’, ‘flood-color’, ‘lighting-color’ apply [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: depends on user agent


Input: [Name] color-interpolation [Values] auto | sRGB | linearRGB [Applies to] container elements, graphics elements and ‘animate’ [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: sRGB


Input: [Name] color-rendering [Values] auto | optimizeSpeed | optimizeQuality [Applies to] container elements, graphics elements and ‘animate’ [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] cursor [Values] [ [ ,]* [ auto | crosshair | default | pointer | move | e-resize | ne-resize | nw-resize | n-resize | se-resize | sw-resize | s-resize | w-resize| text | wait | help ] ] [Applies to] container elements and graphics elements [Inh.] yes [Percentages] N/A [Media] visual, interactive [Anim.] yes [Initial value]

Output: auto


Input: [Name] direction [Values] ltr | rtl [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] no [Initial value]

Output: ltr


Input: [Name] display [Values] inline | block | list-item | run-in | compact | marker | table | inline-table | table-row-group | table-header-group | table-footer-group | table-row | table-column-group | table-column | table-cell | table-caption | none [Applies to] ‘svg’, ‘g’, ‘switch’, ‘a’, ‘foreignObject’, graphics elements (including the ‘text’ element) and text sub-elements (i.e., ‘tspan’, ‘textPath’) [Inh.] no [Percentages] N/A [Media] all [Anim.] yes [Initial value]

Output: inline


Input: [Name] dominant-baseline [Values] auto | use-script | no-change | reset-size | ideographic | alphabetic | hanging | mathematical | central | middle | text-after-edge | text-before-edge [Applies to] text content elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] fill [Values] (See Specifying paint) [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: black


Input: [Name] fill-opacity [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] fill-rule [Values] nonzero | evenodd [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: nonzero


Input: [Name] filter [Values] | none [Applies to] container elements and graphics elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]


Input: [Name] flood-color [Values] currentColor | [] [Applies to] ‘feFlood’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: black


Input: [Name] flood-opacity [Applies to] ‘feFlood’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] font [Values] [ [ ‘font-style’ || ‘font-variant’ || ‘font-weight’ ]? ‘font-size’ [ / 'line-height' ]? ‘font-family’ ] | caption | icon | menu | message-box | small-caption | status-bar [Applies to] text content elements [Inh.] yes [Percentages] see individual properties [Media] visual [Anim.] yes [1] [Initial value]

Output: see individual properties


Input: [Name] font-family [Values] [[ | ],]* [ | ] [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: depends on user agent


Input: [Name] font-size [Values] | | | [Applies to] text content elements [Inh.] yes, the computed value is inherited [Percentages] refer to parent element's font size [Media] visual [Anim.] yes [Initial value]

Output: medium


Input: [Name] font-size-adjust [Values] | none [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [1] [Initial value]


Input: [Name] font-stretch [Values] normal | wider | narrower | ultra-condensed | extra-condensed | condensed | semi-condensed | semi-expanded | expanded | extra-expanded | ultra-expanded [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] font-style [Values] normal | italic | oblique [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] font-variant [Values] normal | small-caps [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] font-weight [Values] normal | bold | bolder | lighter | 100 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900 [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] glyph-orientation-horizontal [Values] | [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] no [Initial value]

Output: 0deg


Input: [Name] glyph-orientation-vertical [Values] auto | | [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] no [Initial value]

Output: auto


Input: [Name] image-rendering [Values] auto | optimizeSpeed | optimizeQuality [Applies to] images [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] letter-spacing [Values] normal | [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] lighting-color [Values] currentColor | [] [Applies to] ‘feDiffuseLighting’ and ‘feSpecularLighting’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: white


Input: [Name] line-height [Values] normal | | | [Applies to] ‘text’ elements [Inh.] yes [Percentages] refer to font size of element itself [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] marker [Values] see individual properties [Applies to] ‘path’, ‘line’, ‘polyline’ and ‘polygon’ elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: see individual properties


Input: [Name] marker-end marker-mid marker-start [Values] none | [Applies to] ‘path’, ‘line’, ‘polyline’ and ‘polygon’ elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]


Input: [Name] mask [Values] | none [Applies to] container elements and graphics elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]


Input: [Name] opacity [Applies to] container elements and graphics elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] overflow [Values] visible | hidden | scroll | auto [Applies to] elements which establish a new viewport, ‘pattern’ elements and ‘marker’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: see prose


Input: [Name] paint-order [Values] normal | [ fill || stroke || markers ] [Applies to] graphics elements and text content elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: normal


Input: [Name] pointer-events [Values] bounding-box | visiblePainted | visibleFill | visibleStroke | visible | painted | fill | stroke | all | none [Applies to] container elements, graphics elements and text content child elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: visiblePainted


Input: [Name] shape-rendering [Values] auto | optimizeSpeed | crispEdges | geometricPrecision [Applies to] shapes [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: auto


Input: [Name] stop-color [Values] currentColor | [] [Applies to] ‘stop’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: black


Input: [Name] stop-opacity [Applies to] ‘stop’ elements [Inh.] no [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] stroke [Values] (See Specifying paint) [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]


Input: [Name] stroke-dasharray [Values] none | [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [1] [Initial value]


Input: [Name] stroke-dashoffset [Values] | [Applies to] shapes and text content elements [Inh.] yes [Percentages] refer to the size of the current viewport [Media] visual [Anim.] yes [Initial value]

Output: 0


Input: [Name] stroke-linecap [Values] butt | round | square [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: butt


Input: [Name] stroke-linejoin [Values] miter | round | bevel [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: miter


Input: [Name] stroke-miterlimit [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 4


Input: [Name] stroke-opacity [Applies to] shapes and text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] stroke-width [Values] | [Applies to] shapes and text content elements [Inh.] yes [Percentages] refer to the size of the current viewport [Media] visual [Anim.] yes [Initial value]

Output: 1


Input: [Name] text-anchor [Values] start | middle | end [Applies to] text content elements [Inh.] yes [Percentages] N/A [Media] visual [Anim.] yes [Initial value]

Output: start