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

Output: emptied


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

Output: stalled


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

Output: play


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

Output: pause


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

Output: loadedmetadata


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

Output: loadeddata


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

Output: waiting


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

Output: playing


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

Output: canplay


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

Output: canplaythrough


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

Output: seeking


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

Output: seeked


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

Output: timeupdate


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

Output: ended


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

Output: ratechange


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

Output: durationchange


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

Output: volumechange


Input: [0] Required software [ContentCVS] Follows a client-server approach The client is a plugin for Protégé 4 [Collaborative Protégé]

Output: Follows a client-server approach The client is a plugin for Protégé 3.4.X or WebProtégé

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [0] Editorial workflow [ContentCVS] Works like a version control system (CVS/SVN): Export, check-out, update, and commit [Collaborative Protégé]

Output: Two modes: Concurrent edition Several users can edit the ontology concurrently Requires a server Sequential edition Only one user can edit the ontology and then it "passes" the files to another one Does not require a server

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [0] Functionalities [ContentCVS] Granularity of axiom and of ontology element Does not support annotations (on commits or on ontology elements) Find local changes with respect to the repository (structural and semantic differences) Conflict detection and resolution Preview the logic consequences of changes [Collaborative Protégé]

Output: Granularity of ontology element Annotate ontology elements and changes (stores user name and timestamp) Search annotations Track changes Voting mechanisms Chat with other users

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [0] Ontology languages [ContentCVS] OWL [Collaborative Protégé]

Output: OWL, RDF(S), or Protégé's Frames model

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [0] Status [ContentCVS] Version 1.2.101 released at February 24, 2009; plugin Tested for Protege 4 build 101 Revision for Build 108 is being adapted [Collaborative Protégé]

Output: Included in the latest Protégé 3.X version: Protege 3.4.1 (build 537) released at June 18th 2009 Further versions are expected to appear

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [0] Support [ContentCVS] Contact the developers [Collaborative Protégé]

Output: Contact the developers Protégé mailing lists

Review of collaborative ontology edition tools - Semantic Sensor Network Incubator Group


Input: [Defining Document] SML [Feature (short)Name] smlref [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: SML references

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetRequired [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Target required

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetType [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Target type

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] derefNV [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Deref outside of validator

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] acyclic [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Acyclic

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetElement [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Target element

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] rules [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Rules (embedded in schemas + rule documents)

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] idConstraint [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: sml:key, keyref, unique

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] validation [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: validation

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] Base64 [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Base64

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] Embedded [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Embedded or By-Value Documents

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] smlifBaseUri [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: smlif:baseuri.

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] schemaComplete [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Schema complete

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] aliases [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Aliases

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] xmlBase [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] no [Feature Description]

Output: xml:base

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] ruleBindings [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Rule bindings

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] smlifVersion [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Consumers must attempt to process regardless of document version contents

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] baseUri [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft] yes [Feature Description]

Output: Establish base URI if any relative references

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] locid [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] no [Feature Description]

Output: Localization resource ID

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] dtdID [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] no [Feature Description]

Output: DTD-defined IDs can be used as bare names in SML references

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] locator [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] no [Feature Description]

Output: Documents can be referred to instead of being embedded in-line

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] schemaBindings [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft] no [Feature Description]

Output: Subsets of the model's definition section's schema documents can be used to assess instance validity

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] smlref [Feature Description] SML references [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetRequired [Feature Description] Target required [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetType [Feature Description] Target type [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] derefNV [Feature Description] Deref outside of validator [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] acyclic [Feature Description] Acyclic [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] targetElement [Feature Description] Target element [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] rules [Feature Description] Rules (embedded in schemas + rule documents) [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] idConstraint [Feature Description] sml:key, keyref, unique [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] validation [Feature Description] validation [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] Base64 [Feature Description] Base64 [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] Embedded [Feature Description] Embedded or By-Value Documents [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] smlifBaseUri [Feature Description] smlif:baseuri. [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] schemaComplete [Feature Description] Schema complete [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] aliases [Feature Description] Aliases [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] xmlBase [Feature Description] xml:base [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: no

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] ruleBindings [Feature Description] Rule bindings [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] smlifVersion [Feature Description] Consumers must attempt to process regardless of document version contents [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] baseUri [Feature Description] Establish base URI if any relative references [Feature Type] Required [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: yes

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] locid [Feature Description] Localization resource ID [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: no

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML [Feature (short)Name] dtdID [Feature Description] DTD-defined IDs can be used as bare names in SML references [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: no

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] locator [Feature Description] Documents can be referred to instead of being embedded in-line [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: no

W3C SML Working Group Feature Implementation Report


Input: [Defining Document] SML-IF [Feature (short)Name] schemaBindings [Feature Description] Subsets of the model's definition section's schema documents can be used to assess instance validity [Feature Type] Optional [Supported by Eclipse COSMOS] yes [Supported by Microsoft]

Output: no

W3C SML Working Group Feature Implementation Report


Input: [INDEX_SIZE_ERR] HIERARCHY_REQUEST_ERR

Output: If any Node is inserted somewhere it doesn't belong.

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] WRONG_DOCUMENT_ERR

Output: If a node is used in a different document than the one that created it (that doesn't support it)

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] NO_MODIFICATION_ALLOWED_ERR

Output: If an attempt is made to modify an object where modifications are not allowed.

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] NOT_FOUND_ERR

Output: If an attempt is made to reference a node in a context where it does not exist .

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] NOT_SUPPORTED_ERR

Output: If the implementation does not support the requested type of object or operation.

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] INVALID_MODIFICATION_ERR

Output: If an attempt is made to modify the type of the underlying object.

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] INVALID_ACCESS_ERR

Output: If a parameter or an operation is not supported by the underlying object.

If index or size is negative, or greater than the allowed value.


Input: [INDEX_SIZE_ERR] TYPE_MISMATCH_ERR

Output: If the type of an object is incompatible with the expected type of the parameter associated to the object.

If index or size is negative, or greater than the allowed value.


Input: [Level] 1. [testability of specification]

Output: Working Group plans regular specification reviews for testability, following Specification Guidelines


Input: [Level] 2. [extent of test materials] Working Group commits that test suite for the specification, not necessarily complete and thorough, will exist before specification becomes Recommendation. [testability of specification]

Output: In addition to the regular specifications reviews mentioned in the previous level, Working Group commits to develop a set of test assertions, not necessarily complete, before beginning development of a test suite.


Input: [Level] 3. [extent of test materials] In addition to the commitment of the previous level, a Working Group ensures that the test suite produced is reviewed by the Working Group or externally and the review process meets the criteria established in this document. [testability of specification]

Output: In addition to regular specification reviews, a Working Group aims to have numerous normative use cases in the body of the Recommendation.


Input: [Level] 4. [extent of test materials] Working Group commits to establish and maintain the test cases contribution and review process and will produce and review the test suite, not necessarily complete and thorough, before the specification becomes Recommendation. [testability of specification]

Output: Same as above.


Input: [Level] 5. [extent of test materials] Same as above [testability of specification]

Output: In addition to the commitments from the previous level, Working Group will derive the list of testable assertions as an addendum to specification by the time it becomes Recommendation.


Input: [Level] 6. [extent of test materials] In addition to the commitment for the previous level, a Working Group insists on a complete test suite before corresponding standard becomes Recommendation. [testability of specification]

Output: Same as above


Input: [Level] 7. [extent of test materials] In addition to the commitment for the previous level, Working Group plans to maintain the test suite even after Specification becomes recommendation. Working Group plans to support versioning and errata in the test suite and review appeals. [testability of specification]

Output: Same as above


Input: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action]

Output: Initiate the drag-and-drop operation

7.7 Drag and drop — HTML5 (Edition for Web Authors)


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action]

Output: Continue the drag-and-drop operation

7.7 Drag and drop — HTML5 (Edition for Web Authors)


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action]

Output: Reject immediate user selection as potential target element

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

7.7 Drag and drop — HTML5 (Edition for Web Authors)


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action]

Output: Reset the current drag operation to "none"

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: Varies

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: Varies

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: yes


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

Output: yes


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

Output: no


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

Output: yes


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

Output: no


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

Output: yes


Input: [Property] address [Expected Type] PostalAddress [Description]

Output: Physical address of the item.

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


Input: [Property] aggregateRating [Expected Type] aggregateRating [Description]

Output: The overall rating, based on a collection of reviews or ratings, of the item.

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


Input: [Property] geo [Expected Type] GeoCoordinates or GeoShape [Description]

Output: The geo coordinates of the place.

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


Input: [Property] map [Expected Type] URL [Description]

Output: A URL to a map of the place.

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


Input: [Property] photos [Expected Type] ImageObject or Photograph [Description]

Output: Photographs of this place

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


Input: [Property] reviews [Expected Type] Review [Description]

Output: Review of the item

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


Input: [Property] telephone [Expected Type] Text [Description]

Output: The telephone number.

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


Input: [Event] connection.disconnect.hangup [Reason] The caller hung up. [Action]

Output: caller disconnects

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1

Table 11: Consultation Transfer Outcomes Prior to Connection Being Established


Input: [Value of form item variable] near_end_disconnect [Reason] The caller canceled the transfer attempt via a DTMF or voice command before the outgoing call begins (during playback of queued audio). [Action]

Output: caller cancels transfer before outgoing call begins

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] busy [Reason] The callee was busy. [Action]

Output: callee busy

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] network_busy [Reason] An intermediate network refused the call. [Action]

Output: network busy

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] noanswer [Reason] There was no answer within the time specified by the connecttimeout attribute. [Action]

Output: callee does not answer

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] unknown [Reason] The transfer ended but the reason is not known. [Action]

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Title] Valid copyright Element With One No Language Tagged text Element [Assertion]

Output: The copyright element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With One Language Tagged text Element [Assertion]

Output: The copyright element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 1 [Assertion]

Output: The copyright element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 2 [Assertion]

Output: The copyright element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One copyright Element [Assertion]

Output: The copyright element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No text Element in copyright Element [Assertion]

Output: The copyright element does not contain a text child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element [Assertion]

Output: The copyright element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element [Assertion]

Output: The copyright element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in copyright Element [Assertion]

Output: The copyright element contains content. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element text Element [Assertion]

Output: The copyright element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element text Element [Assertion]

Output: The copyright element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Pattern] * [Meaning] any element [Described in section]

Output: Universal selector


Input: [Pattern] E [Meaning] an element of type E [Described in section]

Output: Type element selector


Input: [Pattern] E[foo] [Meaning] an E element with the "foo" attribute set [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo="warning"] [Meaning] an E element whose "foo" attribute value is exactly equal to "warning" [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo~="warning"] [Meaning] an E element whose "foo" attribute value is a list of space-separated values, one of which is exactly equal to "warning" [Described in section]

Output: Attribute selectors


Input: [Pattern] E[lang|="en"] [Meaning] an E element whose "lang" attribute has a hyphen-separated list of values beginning (from the left) with "en" [Described in section]

Output: Attribute selectors


Input: [Pattern] E:root [Meaning] an E element, root of the document [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:first-child [Meaning] an E element, first child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-first-child [Meaning] an E element, not the first child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:last-child [Meaning] an E element, last child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-last-child [Meaning] an E element, not the last child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:first-of-type [Meaning] an E element, first sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-first-of-type [Meaning] an E element, not the first sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:last-of-type [Meaning] an E element, last sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-last-of-type [Meaning] an E element, not the last sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:only-of-type [Meaning] an E element, only sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-only-of-type [Meaning] an E element, not the only sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:only-child [Meaning] an E element, only child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-only-child [Meaning] an E element, not the only child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:nth-child(n) [Meaning] an E element, the n-th child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:nth-of-type(n) [Meaning] an E element, the n-th sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:link E:visited [Meaning] an E element being the source anchor of a hyperlink of which the target is not yet visited (:link) or already visited (:visited) [Described in section]

Output: The link pseudo-classes


Input: [Pattern] E:active E:hover E:focus [Meaning] an E element during certain user actions [Described in section]

Output: The user action pseudo-classes


Input: [Pattern] E:target [Meaning] an E element being the target of the refering URI containing a fragment identifier [Described in section]

Output: The target pseudo-class


Input: [Pattern] E:lang(c) [Meaning] an element of type E in (human) language c (the document language specifies how language is determined) [Described in section]

Output: The :lang() pseudo-class


Input: [Pattern] E:enabled E:disabled [Meaning] a user interface element E which is enabled or disabled [Described in section]

Output: The UI element states pseudo-classes


Input: [Pattern] E:checked E:indeterminate [Meaning] a user interface element E which is checked or and indeterminated checked state (for instance a radio-button or checkbox) [Described in section]

Output: The UI element states pseudo-classes


Input: [Pattern] E:subject [Meaning] an E element that is a subject of the selector the current simple selectors belong to [Described in section]

Output: The subject element pseudo-class


Input: [Pattern] E:first-line [Meaning] the first formatted line of an E element [Described in section]

Output: The :first-line pseudo-element


Input: [Pattern] E:first-letter [Meaning] the first formatted letter of an E element [Described in section]

Output: The :first-letter pseudo-element


Input: [Pattern] E:selection [Meaning] the portion of an E element that is currently selected/highlighted by the user [Described in section]

Output: The UI element fragments pseudo-elements


Input: [Pattern] E:menu [Meaning] the generated menu attached to an E element [Described in section]

Output: The UI element fragments pseudo-elements


Input: [Pattern] E:before [Meaning] generated content before an E element [Described in section]

Output: The :before pseudo-element


Input: [Pattern] E:after [Meaning] generated content after an E element [Described in section]

Output: The :after pseudo-element


Input: [Pattern] E.warning [Meaning] HTML only. The same as E[class~="warning"]. [Described in section]

Output: Class selectors


Input: [Pattern] E#myid [Meaning] an E element, its ID being equal to "myid". [Described in section]

Output: ID selectors


Input: [Pattern] E:contains("foo") [Meaning] an E element containing substring "foo" in its textual contents [Described in section]

Output: Content pseudo-class


Input: [Pattern] E F [Meaning] an F element descendant of an E element [Described in section]

Output: Descendant combinator


Input: [Pattern] E > F [Meaning] an F element child of an element E [Described in section]

Output: Child combinator


Input: [Pattern] E + F [Meaning] an F element immediately preceded by an element E [Described in section]

Output: Direct adjacent combinator


Input: [Pattern] E ~ F [Meaning] an F element preceded by an element E [Described in section]

Output: Indirect adjacent combinator


Input: [Title] Valid credits Element With Single credit Element [Assertion]

Output: The credits element matches the schema and it contains one credit child element. This should be linked to a testable assertion in the spec.


Input: [Title] Valid credits Element With Two credit Elements [Assertion]

Output: The credits element matches the schema and it contains two credit child elements. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One credits Element [Assertion]

Output: The credits element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No credit Element in credits Element [Assertion]

Output: The credits element does not contain a credit child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in credits Element [Assertion]

Output: The credits element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in credits Element [Assertion]

Output: The credits element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in credits Element [Assertion]

Output: The credits element contains an content. This should be linked to a testable assertion in the spec.


Input: [Assertion] The uniqueid element matches the schema. [Title]

Output: Valid uniqueid Element


Input: [Assertion] The uniqueid element doesn't exist. This should be linked to a testable assertion in the spec. [Title]

Output: No uniqueid Element


Input: [Assertion] The uniqueid element occurs twice. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One uniqueid Element


Input: [Assertion] The uniqueid element does not contain the required id attribute. This should be linked to a testable assertion in the spec. [Title]

Output: No id Attribute in uniqueid Element


Input: [Assertion] The uniqueid element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in uniqueid Element


Input: [Assertion] The uniqueid element contains a child element. This should be linked to a testable assertion in the spec. [Title]

Output: Child Element in uniqueid Element


Input: [Assertion] The uniqueid element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in uniqueid Element


Input: [Name] equals [Details]

Output: A equals B tests if the geometries are spatially equal. More formally, their symmetric difference MUST be empty. The test for equivalence may be limited to the resolution of the coordinate system or the accuracy of the data.


Input: [Name] disjoint [Details]

Output: A disjoint B tests if A and B have NO points in common.


Input: [Name] intersects [Details]

Output: A intersects B tests if A and B have ANY points in common.


Input: [Name] crosses [Details]

Output: A crosses B if their interiors intersect with a dimension less that the larger of the dimension of A or B and the intersection of the interior of a with the exterior of B is not null (so for two lines, the intersection has to be at a finite number of points). Surfaces cannot cross anything. Points cannot be crossed by anything.


Input: [Name] overlaps [Details]

Output: A overlaps B tests if part of their respective interiors intersect, and if this intersection is the same dimension as the interiors of the original geometries. (This last bit rules out crosses). Some of their interior MUST intersect with the exterior of the other one and vice versa (i.e., one cannot be within the other). This bit rules out within and contains. Overlap only applies if the two geometries are of the same dimension.


Input: [Name] within [Details]

Output: A within B if their intersection equals A. e.g. a POI describing a store may state that it is contained within a shopping mall.


Input: [Name] contains [Details]

Output: A contains B is equivalent to B within A. e.g. a POI describing a mall may state that it contains POIs for each store that is within the mall.


Input: [Name] touches [Details]

Output: A touches B means one's boundary intersects with the other's interior or boundary. Interiors cannot intersect. Points cannot touch. e.g. a POI representing a store within a mall may state that it is next door to another POI which represents the store next door.


Input: [Details] a identical POI. Often used as a permalink [Name]

Output: alternate


Input: [Details] the preferred version of a set of POIs with highly similar content. For example, there could be many different perceptions of a neighborhood boundary POI, but the city's neighborhood map could be the canonical version of this POI. [Name]

Output: canonical


Input: [Details] a copyright statement that applys to the link's context [Name]

Output: copyright


Input: [Details] more information about this POI [Name]

Output: describedby


Input: [Details] a resource that can be used to edit the POI's context [Name]

Output: edit


Input: [Details] a related resource that is potentially large and might require special handling [Name]

Output: enclosure


Input: [Name]

Output: icon


Input: [Details] points to a resource containing the latest version [Name]

Output: latest-version


Input: [Details] a license for this POI [Name]

Output: license


Input: [Details] a related resource [Name]

Output: related


Input: [Details] a resource that can be used to search through the link's context and related resources [Name]

Output: search


Input: [Details] a parent POI, often the enclosing geographic entity, or the entity this POI in under the domain of (such as a field office-corporate headquarters relationship) [Name]

Output: parent


Input: [Details] a child POI, often a geography entity enclosed or under the domain of this POI [Name]

Output: child


Input: [Details] links to a POI or other web resource that describes this place at a previous point in time [Name]

Output: historic


Input: [Details] links to a POI or other web resource that describes this place at a later point in time [Name]

Output: future


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

Output: DECIMAL

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: SMALLINT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: INTEGER

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: BIGINT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: FLOAT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] BINARY LARGE OBJECT [1]

Output: REAL

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [0] NUMERIC [1]

Output: DOUBLE PRECISION

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Terminology [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] None [Overriding] Not applicable

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Elements Within Text [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Control Type] Text input (including date/time and password fields) [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Checkbox [LiveCycle Placement Rules]

Output: Default placement for the label is to the right of the check box.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Radio button group [LiveCycle Placement Rules]

Output: Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Combo box [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control..

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] List box [LiveCycle Placement Rules]

Output: Default placement for the label is above the list box.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Button [LiveCycle Placement Rules]

Output: LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Assertion] The credits element matches the schema and it contains one credit child element. This should be linked to a testable assertion in the spec. [Title]

Output: Valid credits Element With Single credit Element


Input: [Assertion] The credits element matches the schema and it contains two credit child elements. This should be linked to a testable assertion in the spec. [Title]

Output: Valid credits Element With Two credit Elements


Input: [Assertion] The credits element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One credits Element


Input: [Assertion] The credits element does not contain a credit child element. This should be linked to a testable assertion in the spec. [Title]

Output: No credit Element in credits Element


Input: [Assertion] The credits element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in credits Element


Input: [Assertion] The credits element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in credits Element


Input: [Assertion] The credits element contains an content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in credits Element


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Data category]

Output: Translate

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Data category]

Output: Localization Note

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable [Data category]

Output: Terminology

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Data category]

Output: Directionality

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] None [Overriding] Not applicable [Data category]

Output: Ruby

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Data category]

Output: Language Information

Internationalization Tag Set (ITS) Version 2.0


Input: [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable [Data category]

Output: Elements Within Text

Internationalization Tag Set (ITS) Version 2.0


Input: [Numerical Code] 200 [Textual Description] OK [Example]

Output: property delivered correctly


Input: [Numerical Code] 204 [Textual Description] No Content [Example]

Output: property retrieved without content


Input: [Numerical Code] 206 [Textual Description] Partial Content [Example]

Output: only a subset of the available data stored in the result set


Input: [Numerical Code] 400 [Textual Description] Bad Request [Example]

Output: syntactical error


Input: [Numerical Code] 404 [Textual Description] Not Found [Example]

Output: the queries resource is not found


Input: [Numerical Code] 415 [Textual Description] Unsupported Media Type [Example]

Output: get duration call on an image data store


Input: [Numerical Code] 462 [Textual Description] Property not defined in Source Format [Example]

Output: location is not defined in MediaRSS


Input: [Numerical Code] 500 [Textual Description] Internal Server Error [Example]

Output: internal library (e.g., extractor) crashes


Input: [Numerical Code] 562 [Textual Description] Property not supported [Example]

Output: a subset of properties implemented


Input: [Assertion] The uniqueid element matches the schema. [Title]

Output: Valid licensee Element


Input: [Assertion] The uniqueid element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One licensee Element


Input: [Assertion] The uniqueid element does not contain the required name attribute. This should be linked to a testable assertion in the spec. [Title]

Output: No name Attribute in licensee Element


Input: [Assertion] The uniqueid element occures more than once. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in licensee Element


Input: [Assertion] The uniqueid element contains a child element. This should be linked to a testable assertion in the spec. [Title]

Output: Child Element in licensee Element


Input: [Assertion] The uniqueid element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in licensee Element


Input: [ID] 1 [Location] 5.2 [Subject] Lexical space for XForms data types missing [Followup] FS [Ed. / Subs.] S [Comment]

Output: The description of the XForms data types does not in every case provide information about the lexical space(s), but only about the value spaces. Please provide a statement describing the relation.


Input: [ID] 2 [Location] 5.2.3 and 5.2.4 [Subject] Reference to definition of data types missing [Followup] FS [Ed. / Subs.] S [Comment]

Output: The data types dateTimeDuration and yearMonthDuration are described as XForms data types, but they are data types defined in the XQuery Data Model specification. Please provide a reference to this specification from sec. 5.2.3 and 5.2.4. See also the related comment from the XML Core WG, which is basically the same.


Input: [ID] 3 [Location] 2 [Subject] Mention of Internationalization [Followup] FS [Ed. / Subs.] S [Comment]

Output: Internationalization Using XML 1.0 for instance data ensures that the submitted data is internationalization ready. We think that XForms should refer to XML 1.1 as well.


Input: [ID] 4 [Location] 3.2.2 [Subject] Responsibility for useability of IRIs unclear [Followup] FS [Ed. / Subs.] S [Comment]

Output: The host language may permit a Linking Attributes Collection to be applied to XForms elements as an alternate means of obtaining content related to the element. An example is the src attribute from [XHTML 1.0]. The schedule by which link traversal occurs is defined by the host language. If the link traversal fails, the host language may dispatch xforms-link-exception or xforms-link-error to the model associated with the in-scope evaluation context node of the element that bears the Linking Attributes Collection for the failed link. Does this mean that the host language is responsible whether XForms allows for using IRIs or not? Please answer this question in the specification and provide a reference (normative or informative, depending on the answer) to the IRI specification.


Input: [ID] 5 [Location] 4.2.1 [Subject] IRIs for external schema locations possible? [Followup] FS [Ed. / Subs.] S [Comment]

Output: As part of the xforms-model-construct Event, you describe that all XML Schemas are loaded. Is it possible to use IRIs for identifying external schemas? See also comment 4 of the i18n core comments.


Input: [ID] 6 [Location] 5.2.5 [Subject] Restriction of international mail addresses unclear [Followup] FS [Ed. / Subs.] S [Comment]

Output: Internationalized email addresses are not restricted by XForms beyond the definition in the RFC. Please clarify whether it is possible to use internationalized email or not. We feel that it would be important that it is possible.


Input: [ID] 7 [Location] 7.10.1 [Subject] Require UTC as default for time zone information [Followup] FS [Ed. / Subs.] S [Comment]

Output: The now function returns the current system date and time as a string value in the canonical XML Schema xsd:dateTime format. If time zone information is available, it is included (normalized to UTC). If no time zone information is available, an implementation default is used. Please require that the default is UTC. Otherwise the results of applying this function by different implementations might lead to dateTime values which are not totally ordered. See the Working with Time Zones for further guidance. Btw., in e.g. sec. 7.10.2 "The days-from-date() Function" you already require usage of UTC.


Input: [ID] 8. [Location] 7.10.6 and 7.10.7 [Subject] Availability of time zone information unclear [Followup] FS [Ed. / Subs.] S [Comment]

Output: Sec. 7.10.6 contains the statement: This function returns a lexical xsd:date obtained as if by the following rules: the result of now() is converted to a local date based on the user agent time zone information. From this statement it is unclear what kind of indicator the user agent should use to provide time zone information. The same unclearness is in sec.7.10.7.


Input: [ID] 9 [Location] App. E [Subject] Add scripts to XForms input-mode script list in Appendix E [Followup] MD [Ed. / Subs.] S [Comment]

Output: The Working Group endorses the coment sent by Martin Dürst at http://lists.w3.org/Archives/Public/www-forms-editor/2007Mar/0010.html. Please keep us in the loop during your discussion of the comment.


Input: [ID] 10 [Location] Various [Subject] Various [Followup] YS [Ed. / Subs.] S [Comment]

Output: The Working Group endorses the coment sent by Yves Savourel http://lists.w3.org/Archives/Public/www-forms-editor/2007Mar/0009.html , especially comment 1 ("Is the WG planning to provide an ITS Rule file along with the specification (e.g. as a non-normative appendix)?") Please keep us in the loop during your discussion of the comments.


Input: [Assertion] The copyright element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With One No Language Tagged text Element


Input: [Assertion] The copyright element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With One Language Tagged text Element


Input: [Assertion] The copyright element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With Mixed text Element Language Tags 1


Input: [Assertion] The copyright element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With Mixed text Element Language Tags 2


Input: [Assertion] The copyright element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One copyright Element


Input: [Assertion] The copyright element does not contain a text child element. This should be linked to a testable assertion in the spec. [Title]

Output: No text Element in copyright Element


Input: [Assertion] The copyright element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in copyright Element


Input: [Assertion] The copyright element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in copyright Element


Input: [Assertion] The copyright element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in copyright Element


Input: [Assertion] The copyright element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in copyright Element text Element


Input: [Assertion] The copyright element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in copyright Element text Element


Input: [Data category] Translate [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Note [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Terminology [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Directionality [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Ruby [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Language Information [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Elements Within Text [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Title] Valid uniqueid Element [Assertion]

Output: The uniqueid element matches the schema.


Input: [Title] No uniqueid Element [Assertion]

Output: The uniqueid element doesn't exist. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One uniqueid Element [Assertion]

Output: The uniqueid element occurs twice. This should be linked to a testable assertion in the spec.


Input: [Title] No id Attribute in uniqueid Element [Assertion]

Output: The uniqueid element does not contain the required id attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in uniqueid Element [Assertion]

Output: The uniqueid element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Child Element in uniqueid Element [Assertion]

Output: The uniqueid element contains a child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in uniqueid Element [Assertion]

Output: The uniqueid element contains content. This should be linked to a testable assertion in the spec.


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

Output: CHARACTER

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [1] SMALLINT [2] DATE [0]

Output: CHARACTER VARYING

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [1] INTEGER [2] TIME [0]

Output: CHARACTER LARGE OBJECT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: BINARY

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [1] FLOAT [2] INTERVAL [0]

Output: BINARY VARYING

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [1] REAL [0]

Output: BINARY LARGE OBJECT

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


Input: [1] DOUBLE PRECISION [0]

Output: NUMERIC

Mapping SQL datatypes to XML Schema datatypes - RDB2RDF


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

Output: Confidentiality

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Request Authentication

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Response Authentication

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Persistent Authentication

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Message Correspondence

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Request Replay

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Denial of Service

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Name] alternate [Details]

Output: a identical POI. Often used as a permalink


Input: [Name] canonical [Details]

Output: the preferred version of a set of POIs with highly similar content. For example, there could be many different perceptions of a neighborhood boundary POI, but the city's neighborhood map could be the canonical version of this POI.


Input: [Name] copyright [Details]

Output: a copyright statement that applys to the link's context


Input: [Name] describedby [Details]

Output: more information about this POI


Input: [Name] edit [Details]

Output: a resource that can be used to edit the POI's context


Input: [Name] enclosure [Details]

Output: a related resource that is potentially large and might require special handling


Input: [Name] latest-version [Details]

Output: points to a resource containing the latest version


Input: [Name] license [Details]

Output: a license for this POI


Input: [Name] related [Details]

Output: a related resource


Input: [Name] search [Details]

Output: a resource that can be used to search through the link's context and related resources


Input: [Name] parent [Details]

Output: a parent POI, often the enclosing geographic entity, or the entity this POI in under the domain of (such as a field office-corporate headquarters relationship)


Input: [Name] child [Details]

Output: a child POI, often a geography entity enclosed or under the domain of this POI


Input: [Name] historic [Details]

Output: links to a POI or other web resource that describes this place at a previous point in time


Input: [Name] future [Details]

Output: links to a POI or other web resource that describes this place at a later point in time


Input: [ID] 1 [Location] 5.2 [Comment] The description of the XForms data types does not in every case provide information about the lexical space(s), but only about the value spaces. Please provide a statement describing the relation. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Lexical space for XForms data types missing


Input: [ID] 2 [Location] 5.2.3 and 5.2.4 [Comment] The data types dateTimeDuration and yearMonthDuration are described as XForms data types, but they are data types defined in the XQuery Data Model specification. Please provide a reference to this specification from sec. 5.2.3 and 5.2.4. See also the related comment from the XML Core WG, which is basically the same. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Reference to definition of data types missing


Input: [ID] 3 [Location] 2 [Comment] Internationalization Using XML 1.0 for instance data ensures that the submitted data is internationalization ready. We think that XForms should refer to XML 1.1 as well. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Mention of Internationalization


Input: [ID] 4 [Location] 3.2.2 [Comment] The host language may permit a Linking Attributes Collection to be applied to XForms elements as an alternate means of obtaining content related to the element. An example is the src attribute from [XHTML 1.0]. The schedule by which link traversal occurs is defined by the host language. If the link traversal fails, the host language may dispatch xforms-link-exception or xforms-link-error to the model associated with the in-scope evaluation context node of the element that bears the Linking Attributes Collection for the failed link. Does this mean that the host language is responsible whether XForms allows for using IRIs or not? Please answer this question in the specification and provide a reference (normative or informative, depending on the answer) to the IRI specification. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Responsibility for useability of IRIs unclear


Input: [ID] 5 [Location] 4.2.1 [Comment] As part of the xforms-model-construct Event, you describe that all XML Schemas are loaded. Is it possible to use IRIs for identifying external schemas? See also comment 4 of the i18n core comments. [Followup] FS [Ed. / Subs.] S [Subject]

Output: IRIs for external schema locations possible?


Input: [ID] 6 [Location] 5.2.5 [Comment] Internationalized email addresses are not restricted by XForms beyond the definition in the RFC. Please clarify whether it is possible to use internationalized email or not. We feel that it would be important that it is possible. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Restriction of international mail addresses unclear


Input: [ID] 7 [Location] 7.10.1 [Comment] The now function returns the current system date and time as a string value in the canonical XML Schema xsd:dateTime format. If time zone information is available, it is included (normalized to UTC). If no time zone information is available, an implementation default is used. Please require that the default is UTC. Otherwise the results of applying this function by different implementations might lead to dateTime values which are not totally ordered. See the Working with Time Zones for further guidance. Btw., in e.g. sec. 7.10.2 "The days-from-date() Function" you already require usage of UTC. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Require UTC as default for time zone information


Input: [ID] 8. [Location] 7.10.6 and 7.10.7 [Comment] Sec. 7.10.6 contains the statement: This function returns a lexical xsd:date obtained as if by the following rules: the result of now() is converted to a local date based on the user agent time zone information. From this statement it is unclear what kind of indicator the user agent should use to provide time zone information. The same unclearness is in sec.7.10.7. [Followup] FS [Ed. / Subs.] S [Subject]

Output: Availability of time zone information unclear


Input: [ID] 9 [Location] App. E [Comment] The Working Group endorses the coment sent by Martin Dürst at http://lists.w3.org/Archives/Public/www-forms-editor/2007Mar/0010.html. Please keep us in the loop during your discussion of the comment. [Followup] MD [Ed. / Subs.] S [Subject]

Output: Add scripts to XForms input-mode script list in Appendix E


Input: [ID] 10 [Location] Various [Comment] The Working Group endorses the coment sent by Yves Savourel http://lists.w3.org/Archives/Public/www-forms-editor/2007Mar/0009.html , especially comment 1 ("Is the WG planning to provide an ITS Rule file along with the specification (e.g. as a non-normative appendix)?") Please keep us in the loop during your discussion of the comments. [Followup] YS [Ed. / Subs.] S [Subject]

Output: Various


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

Output: yes


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

Output: yes


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

Output: no


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

Output: yes


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

Output: no


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

Output: yes


Input: [Language feature] a element that creates a hyperlink [Restrictions] Role must be either link, button, checkbox, menuitem, menuitemcheckbox, menuitemradio, tab, or treeitem [Default implied ARIA semantic]

Output: link role


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main [Default implied ARIA semantic]

Output: article role


Input: [Language feature] aside element [Restrictions] Role must be either note, complementary, or search [Default implied ARIA semantic]

Output: note role


Input: [Language feature] audio element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] button element [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group role


Input: [Language feature] embed element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] h1 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h2 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h3 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h4 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h5 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h6 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] header element [Restrictions] If specified, role must be banner [Default implied ARIA semantic]

Output: No role


Input: [Language feature] iframe element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] img element whose alt attribute's value is present and not empty [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] input element with a type attribute in the Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] Role must be either checkbox or menuitemcheckbox [Default implied ARIA semantic]

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Image Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] Role must be either radio or menuitemradio [Default implied ARIA semantic]

Output: radio role


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] Role must be either listitem, menuitemcheckbox, menuitemradio, option, tab, or treeitem [Default implied ARIA semantic]

Output: listitem role


Input: [Language feature] object element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] ol element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions [Default implied ARIA semantic]

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: region role


Input: [Language feature] ul element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] video element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] The body element [Restrictions] Role must be either document or application [Default implied ARIA semantic]

Output: document role


Input: [Title] Valid licensee Element [Assertion]

Output: The uniqueid element matches the schema.


Input: [Title] More Than One licensee Element [Assertion]

Output: The uniqueid element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No name Attribute in licensee Element [Assertion]

Output: The uniqueid element does not contain the required name attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in licensee Element [Assertion]

Output: The uniqueid element occures more than once. This should be linked to a testable assertion in the spec.


Input: [Title] Child Element in licensee Element [Assertion]

Output: The uniqueid element contains a child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in licensee Element [Assertion]

Output: The uniqueid element contains content. This should be linked to a testable assertion in the spec.


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: [Assertion] The description element matches the schema. [Title]

Output: Valid description Element


Input: [Assertion] The description element does not contain a url attribute but it still matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element Without url Attribute


Input: [Assertion] The description element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With One No Language Tagged text Element


Input: [Assertion] The description element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With One Language Tagged text Element


Input: [Assertion] The description element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With Mixed text Element Language Tags 1


Input: [Assertion] The description element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec. [Title]

Output: Valid description Element With Mixed text Element Language Tags 2


Input: [Assertion] The description element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One description Element


Input: [Assertion] The description element does not contain a text child element. This should be linked to a testable assertion in the spec. [Title]

Output: No text Element in description Element


Input: [Assertion] The description element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in description Element


Input: [Assertion] The description element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in description Element


Input: [Assertion] The description element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in description Element


Input: [Assertion] The description element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in description Element text Element


Input: [Assertion] The description element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in description Element text Element


Input: [Pattern] * [Described in section] Universal selector [Meaning]

Output: any element


Input: [Pattern] E [Described in section] Type element selector [Meaning]

Output: an element of type E


Input: [Pattern] E[foo] [Described in section] Attribute selectors [Meaning]

Output: an E element with the "foo" attribute set


Input: [Pattern] E[foo="warning"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "foo" attribute value is exactly equal to "warning"


Input: [Pattern] E[foo~="warning"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "foo" attribute value is a list of space-separated values, one of which is exactly equal to "warning"


Input: [Pattern] E[lang|="en"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "lang" attribute has a hyphen-separated list of values beginning (from the left) with "en"


Input: [Pattern] E:root [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, root of the document


Input: [Pattern] E:first-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, first child of its parent


Input: [Pattern] E:not-first-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the first child of its parent


Input: [Pattern] E:last-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, last child of its parent


Input: [Pattern] E:not-last-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the last child of its parent


Input: [Pattern] E:first-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, first sibling of its type


Input: [Pattern] E:not-first-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the first sibling of its type


Input: [Pattern] E:last-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, last sibling of its type


Input: [Pattern] E:not-last-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the last sibling of its type


Input: [Pattern] E:only-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, only sibling of its type


Input: [Pattern] E:not-only-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the only sibling of its type


Input: [Pattern] E:only-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, only child of its parent


Input: [Pattern] E:not-only-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the only child of its parent


Input: [Pattern] E:nth-child(n) [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, the n-th child of its parent


Input: [Pattern] E:nth-of-type(n) [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, the n-th sibling of its type


Input: [Pattern] E:link E:visited [Described in section] The link pseudo-classes [Meaning]

Output: an E element being the source anchor of a hyperlink of which the target is not yet visited (:link) or already visited (:visited)


Input: [Pattern] E:active E:hover E:focus [Described in section] The user action pseudo-classes [Meaning]

Output: an E element during certain user actions


Input: [Pattern] E:target [Described in section] The target pseudo-class [Meaning]

Output: an E element being the target of the refering URI containing a fragment identifier


Input: [Pattern] E:lang(c) [Described in section] The :lang() pseudo-class [Meaning]

Output: an element of type E in (human) language c (the document language specifies how language is determined)


Input: [Pattern] E:enabled E:disabled [Described in section] The UI element states pseudo-classes [Meaning]

Output: a user interface element E which is enabled or disabled


Input: [Pattern] E:checked E:indeterminate [Described in section] The UI element states pseudo-classes [Meaning]

Output: a user interface element E which is checked or and indeterminated checked state (for instance a radio-button or checkbox)


Input: [Pattern] E:subject [Described in section] The subject element pseudo-class [Meaning]

Output: an E element that is a subject of the selector the current simple selectors belong to


Input: [Pattern] E:first-line [Described in section] The :first-line pseudo-element [Meaning]

Output: the first formatted line of an E element


Input: [Pattern] E:first-letter [Described in section] The :first-letter pseudo-element [Meaning]

Output: the first formatted letter of an E element


Input: [Pattern] E:selection [Described in section] The UI element fragments pseudo-elements [Meaning]

Output: the portion of an E element that is currently selected/highlighted by the user


Input: [Pattern] E:menu [Described in section] The UI element fragments pseudo-elements [Meaning]

Output: the generated menu attached to an E element


Input: [Pattern] E:before [Described in section] The :before pseudo-element [Meaning]

Output: generated content before an E element


Input: [Pattern] E:after [Described in section] The :after pseudo-element [Meaning]

Output: generated content after an E element


Input: [Pattern] E.warning [Described in section] Class selectors [Meaning]

Output: HTML only. The same as E[class~="warning"].


Input: [Pattern] E#myid [Described in section] ID selectors [Meaning]

Output: an E element, its ID being equal to "myid".


Input: [Pattern] E:contains("foo") [Described in section] Content pseudo-class [Meaning]

Output: an E element containing substring "foo" in its textual contents


Input: [Pattern] E F [Described in section] Descendant combinator [Meaning]

Output: an F element descendant of an E element


Input: [Pattern] E > F [Described in section] Child combinator [Meaning]

Output: an F element child of an element E


Input: [Pattern] E + F [Described in section] Direct adjacent combinator [Meaning]

Output: an F element immediately preceded by an element E


Input: [Pattern] E ~ F [Described in section] Indirect adjacent combinator [Meaning]

Output: an F element preceded by an element E


Input: [Details] A equals B tests if the geometries are spatially equal. More formally, their symmetric difference MUST be empty. The test for equivalence may be limited to the resolution of the coordinate system or the accuracy of the data. [Name]

Output: equals


Input: [Details] A disjoint B tests if A and B have NO points in common. [Name]

Output: disjoint


Input: [Details] A intersects B tests if A and B have ANY points in common. [Name]

Output: intersects


Input: [Details] A crosses B if their interiors intersect with a dimension less that the larger of the dimension of A or B and the intersection of the interior of a with the exterior of B is not null (so for two lines, the intersection has to be at a finite number of points). Surfaces cannot cross anything. Points cannot be crossed by anything. [Name]

Output: crosses


Input: [Details] A overlaps B tests if part of their respective interiors intersect, and if this intersection is the same dimension as the interiors of the original geometries. (This last bit rules out crosses). Some of their interior MUST intersect with the exterior of the other one and vice versa (i.e., one cannot be within the other). This bit rules out within and contains. Overlap only applies if the two geometries are of the same dimension. [Name]

Output: overlaps


Input: [Details] A within B if their intersection equals A. e.g. a POI describing a store may state that it is contained within a shopping mall. [Name]

Output: within


Input: [Details] A contains B is equivalent to B within A. e.g. a POI describing a mall may state that it contains POIs for each store that is within the mall. [Name]

Output: contains


Input: [Details] A touches B means one's boundary intersects with the other's interior or boundary. Interiors cannot intersect. Points cannot touch. e.g. a POI representing a store within a mall may state that it is next door to another POI which represents the store next door. [Name]

Output: touches


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


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

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

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Title] Valid description Element [Assertion]

Output: The description element matches the schema.


Input: [Title] Valid description Element Without url Attribute [Assertion]

Output: The description element does not contain a url attribute but it still matches the schema. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With One No Language Tagged text Element [Assertion]

Output: The description element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With One Language Tagged text Element [Assertion]

Output: The description element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With Mixed text Element Language Tags 1 [Assertion]

Output: The description element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid description Element With Mixed text Element Language Tags 2 [Assertion]

Output: The description element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One description Element [Assertion]

Output: The description element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No text Element in description Element [Assertion]

Output: The description element does not contain a text child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in description Element [Assertion]

Output: The description element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in description Element [Assertion]

Output: The description element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in description Element [Assertion]

Output: The description element contains content. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in description Element text Element [Assertion]

Output: The description element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in description Element text Element [Assertion]

Output: The description element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Action] caller disconnects [Event] connection.disconnect.hangup [Reason]

Output: The caller hung up.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] caller cancels transfer before outgoing call begins [Value of form item variable] near_end_disconnect [Reason]

Output: The caller canceled the transfer attempt via a DTMF or voice command before the outgoing call begins (during playback of queued audio).

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] callee busy [Value of form item variable] busy [Reason]

Output: The callee was busy.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] network busy [Value of form item variable] network_busy [Reason]

Output: An intermediate network refused the call.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] callee does not answer [Value of form item variable] noanswer [Reason]

Output: There was no answer within the time specified by the connecttimeout attribute.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] --- [Value of form item variable] unknown [Reason]

Output: The transfer ended but the reason is not known.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Feature] 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: [Feature] 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: [Feature] 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: [Feature] 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