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

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


Input: [User Action/External Input] User presses button on steering wheel [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Action on Device]

Output: Connection to ASR server is established


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


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Action on Device]

Output: Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed


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

Output: Devices sends updated destination information to app server


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

Output: HTTP Request to app server


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

Output: HTTP Request to app server which includes user credentials


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

Output: GPS_Data_In Event


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

Output: Touch_screen_event (includes x, y coordinates)


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

Output: Start_Listening Event


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


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


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

Output: GPS_Data_In Event


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

Output: GPS_Data_In Event


Input: [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


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

Output: Route_Change Alert


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


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

Output: Start_Listening Event


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


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

Output: HTTP requests to app server for dialog and data specific to user response


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Event Description]

Output: HTTP Request for updated directions (based on current location, detour destination, and ultimate destination)


Input: 1. A method of distributing content, comprising: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system.

Output: WARP does not make use of any cryptographic information. WARP does not create a ticket file including the cryptographic hash. WARP does not distribute a ticket file to a user system or anything to the system.

WARP: Widgets Access Request Policy: PAG Report

Claims of the '1146 Application and WARP Features

Evaluation against the WARP Specification


Input: 2. The method of claim 1, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content.

Output: WARP does nothing relating to the above

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 3. The method of claim 1, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification.

Output: WARP does not make use of digital signatures.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 4. The method of claim 3, where initiating a security action comprises: initiating a revocation service.

Output: WARP has no relation to initializing revocation services.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 5. The method of claim 3, where initiating a security action comprises: preventing user systems from downloading the content.

Output: WARP does not rely in cryptographic methods to prevent user systems from downloading content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 6. A method of downloading content from a network, comprising: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content.

Output: WARP does not download any content. WARP does not make use of any cryptographic hashes or any cryptography.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 7. The method of claim 6, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file.

Output: WARP has no relationship to digital signatures or ticket files.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 8. The method of claim 7, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: See above 7.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 9. The method of claim 8, where initiating a security action comprises: deleting the content from the user system. WARP does not interact with the user's system.

Output: WARP does not have the ability to demand that, or have any provisions that would require, content be deleted from the user's system.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 10. The method of claim 8, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file.

Output: WARP has no means to contact other sites on failure.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 11. The method of claim 8, where initiating a security action comprises: scanning the user system for instances of revoked content.

Output: WARP most definitely does not have any provisions to scan the user's hard drive deleting content

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 12. The method of claim 1, further comprising: creating a security log on the user system that includes a history of content installation

Output: WARP does not write anything to the user's hard drive or do any privacy violating things like keeping records of stuff on user's hard drives.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 13. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system.

Output: WARP does not cryptographically do anything… specially nothing relating to content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 14. The computer-readable medium of claim 13, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content.

Output: WARP does not cryptographically do anything… specially nothing relating to content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 15. The computer-readable medium of claim 13, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 16. The computer-readable medium of claim 15, where initiating a security action comprises: initiating a revocation service.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 17. The computer-readable medium of claim 15, where initiating a security action comprises: preventing user systems from downloading the content.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified. Hence this does not apply.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 18. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content.

Output: WARP does not access content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 19. The computer-readable medium of claim 18, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file.

Output: WARP does not access content. WARP does not download or deal with ticket files.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 20. The computer-readable medium of claim 18, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: WARP does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 21. The computer-readable medium of claim 20, where initiating a security action comprises: deleting the content from the user system.

Output: WARP does not do any cryptographic checks. WARP does not do deletion of people's content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 22. The computer-readable medium of claim 20, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file.

Output: WARP does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 23. The computer-readable medium of claim 20, where initiating a security action comprises: scanning the user system for instances of revoked content.

Output: WARP does not do any cryptographic checks. WARP does not do deletion of people's content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 24. The computer-readable medium of claim 18, further comprising: creating a security log on the user system that includes a history of content installation.

Output: WARP does not write log files about their computer's content. WARP does not generate security logs.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 25. A method of installing content, comprising: receiving content from a content distributor, the content including a first cryptographic hash of the content; creating a second cryptographic hash of the content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: WARP does not do this as it does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 26. The method of claim 25, further comprising: comparing the content to one or more lists of content to determine if the content can be safely installed.

Output: WARP does not do this. it has nothing to do with content installation.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: [Identifier] assigner [Semantics] The Party is the issuer of the policy statement [Comment]

Output: Must be supported.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


Input: [Identifier] assignee [Semantics] The Party is the recipient of the policy statement [Comment]

Output: Must be supported.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] attributedParty [Semantics] The Party to be attributed [Comment]

Output: May be specified as part of the attribute action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] consentingParty [Semantics] The Party to obtain consent from [Comment]

Output: May be specified as part of the obtainConsent action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] informedParty [Semantics] The Party to be informed of all uses [Comment]

Output: May be specified as part of the inform action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensatedParty [Semantics] The Party is the recipient of the compensation [Comment]

Output: May be specified as part of the compensate duty action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] trackingParty [Semantics] The Party is the usage tracker [Comment]

Output: May be specified as part of the acceptTracking action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: No conflict

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict

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


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

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

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


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

Output: No conflict

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


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

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

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


Input: [Id: Title] i1 : How to create an XHTML document? [Concerning] XHTML [State]

Output: resolved


Input: [Id: Title] i2 : lack a method to easily access the HEAD element [Concerning] improvement [State]

Output: rejected


Input: [Id: Title] i3 : Convenient methods to create elements [Concerning] improvement [State]

Output: rejected


Input: [Id: Title] i4 : methods that return instances of specific elements should have a specific return type [Concerning] improvement [State]

Output: rejected


Input: [Id: Title] i5 : HTMLFrameElement::src should dynamically update [Concerning] improvement [State]

Output: rejected


Input: [Id: Title] i6 : HTMLFormElement::submit [Concerning] clarification [State]

Output: active


Input: [Id: Title] i7 : HTMLInputElement::size [Concerning] type error [State]

Output: resolved


Input: [Id: Title] i8 : HTMLTableElement: there are tFoot, tHead and caption should be readonly. [Concerning] readwrite/readonly? [State]

Output: rejected


Input: [Id: Title] i9 : select.options.length should be read/write [Concerning] readwrite/readonly? [State]

Output: resolved


Input: [Id: Title] i9b : select.options array [Concerning] array manipulation [State]

Output: rejected


Input: [Id: Title] i10 : HTMLInputElement.indeterminate [Concerning] new property [State]

Output: Subsumed by issue i24


Input: [Id: Title] i11 : XHTML 1.0 [Concerning] General [State]

Output: resolved


Input: [Id: Title] i12 : HTML DOM and DTDs [Concerning] clarifications [State]

Output: resolved


Input: [Id: Title] i13 : XHTML 1.0 DTDs [Concerning] clarification [State]

Output: resolved


Input: [Id: Title] i14 : HTML 4, 4.0, and 4.01 [Concerning] clarification [State]

Output: resolved


Input: [Id: Title] i15 : name or id [Concerning] clarification [State]

Output: resolved


Input: [Id: Title] i16 : HTMLDocument.anchors [Concerning] convenience [State]

Output: resolved


Input: [Id: Title] i17 : HTMLDocument.images [Concerning] convenience [State]

Output: resolved


Input: [Id: Title] i18 : Element.className [Concerning] textual issue [State]

Output: resolved


Input: [Id: Title] i20 : HTMLInputElement.indeterminate, checked and the form itself [Concerning] incompatibility [State]

Output: rejected


Input: [Id: Title] i21 : HTMLSelectElement.add [Concerning] clarification [State]

Output: resolved


Input: [Id: Title] i22 : setting tFoot, tHead and caption [Concerning] clarification [State]

Output: resolved


Input: [Id: Title] i23 : classid [Concerning] HTMLObjectElement [State]

Output: rejected


Input: [Id: Title] i24 : indeterminate [Concerning] technical [State]

Output: active


Input: [Id: Title] i25 : Java package name [Concerning] technical [State]

Output: resolved


Input: [Final] Final [Description] The operation succeeded. [QName Local Name]

Output: Success

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] The service does not support the protocol version specified in the request. [QName Local Name]

Output: VersionMismatch

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred that was due to the message sent by the sender. [QName Local Name]

Output: Sender

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred at the receiver. [QName Local Name]

Output: Receiver

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol [QName Local Name]

Output: Represent

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The request has been accepted for processing and the service will return the result asynchronously [QName Local Name]

Output: Pending

XML Key Management Specification (XKMS 2.0)


Input: [Name] flex-direction [Value] row | row-reverse | column | column-reverse [Initial] row [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] specified value [Applies to]

Output: flex containers


Input: [Name] flex-wrap [Value] nowrap | wrap | wrap-reverse [Initial] nowrap [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] specified value [Applies to]

Output: flex containers


Input: [Name] flex-flow [Value] || [Initial] see individual properties [Inh.] see individual properties [%ages] see individual properties [Media] see individual properties [Animatable] see individual properties [Computed value] see individual properties [Applies to]

Output: see individual properties


Input: [Name] order [Initial] 0 [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value] specified value [Applies to]

Output: flex items and absolutely-positioned children of flex containers


Input: [Name] flex [Value] none | [ <‘flex-grow’> <‘flex-shrink’>? || <‘flex-basis’> ] [Initial] see individual properties [Inh.] see individual properties [%ages] n/a [Media] visual [Animatable] no [Canonical order] per grammar [Computed value] see individual properties [Applies to]

Output: flex items


Input: [Name] flex-grow [Initial] 0 [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value] specified value [Applies to]

Output: flex items


Input: [Name] flex-shrink [Initial] 1 [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value] specified value [Applies to]

Output: flex items


Input: [Name] flex-basis [Value] content | <‘width’> [Initial] auto [Inh.] no [%ages] relative to the flex container’s inner main size [Media] visual [Animatable] as width [Computed value] as specified, with lengths made absolute [Applies to]

Output: flex items


Input: [Name] justify-content [Value] flex-start | flex-end | center | space-between | space-around [Initial] flex-start [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] specified value [Applies to]

Output: flex containers


Input: [Name] align-items [Value] flex-start | flex-end | center | baseline | stretch [Initial] stretch [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] specified value [Applies to]

Output: flex containers


Input: [Name] align-self [Value] auto | flex-start | flex-end | center | baseline | stretch [Initial] auto [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] auto computes to parent’s align-items value; otherwise as specified [Applies to]

Output: flex items


Input: [Name] align-content [Value] flex-start | flex-end | center | space-between | space-around | stretch [Initial] stretch [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value] specified value [Applies to]

Output: multi-line flex containers


Input: [RFC Property] CATEGORIES [Ontology Property] category [N-Ary Property] hasCategory [Note]

Output: The categories of the object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] NOTE [Ontology Property] note [N-Ary Property] hasNote [Note]

Output: Notes about the object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] PRODID [Ontology Property] prodid [Note]

Output: The identifier of the product that created the vCard object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] REV [Ontology Property] rev [Note]

Output: The revision datetime of the vCard object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] SOUND [Ontology Property] hasSound [Note]

Output: Audio related to the object (data URI)

vCard Ontology - for describing People and Organizations


Input: [RFC Property] UID [Ontology Property] hasUID [Note]

Output: A unique identifier for the object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] CLIENTPIDMAP [Note]

Output: Not required

vCard Ontology - for describing People and Organizations


Input: [RFC Property] URL [Ontology Property] hasURL [Note]

Output: Any URL related to the object

vCard Ontology - for describing People and Organizations


Input: [RFC Property] VERSION [Note]

Output: Not required (namespace will capture this)

vCard Ontology - for describing People and Organizations


Input: [Name] flex-direction [Value] row | row-reverse | column | column-reverse [Initial] row [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: specified value


Input: [Name] flex-wrap [Value] nowrap | wrap | wrap-reverse [Initial] nowrap [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: specified value


Input: [Name] flex-flow [Value] || [Initial] see individual properties [Applies to] see individual properties [Inh.] see individual properties [%ages] see individual properties [Media] see individual properties [Animatable] see individual properties [Computed value]

Output: see individual properties


Input: [Name] order [Initial] 0 [Applies to] flex items and absolutely-positioned children of flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value]

Output: specified value


Input: [Name] flex [Value] none | [ <‘flex-grow’> <‘flex-shrink’>? || <‘flex-basis’> ] [Initial] see individual properties [Applies to] flex items [Inh.] see individual properties [%ages] n/a [Media] visual [Animatable] no [Canonical order] per grammar [Computed value]

Output: see individual properties


Input: [Name] flex-grow [Initial] 0 [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value]

Output: specified value


Input: [Name] flex-shrink [Initial] 1 [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Animatable] yes [Computed value]

Output: specified value


Input: [Name] flex-basis [Value] content | <‘width’> [Initial] auto [Applies to] flex items [Inh.] no [%ages] relative to the flex container’s inner main size [Media] visual [Animatable] as width [Computed value]

Output: as specified, with lengths made absolute


Input: [Name] justify-content [Value] flex-start | flex-end | center | space-between | space-around [Initial] flex-start [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: specified value


Input: [Name] align-items [Value] flex-start | flex-end | center | baseline | stretch [Initial] stretch [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: specified value


Input: [Name] align-self [Value] auto | flex-start | flex-end | center | baseline | stretch [Initial] auto [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: auto computes to parent’s align-items value; otherwise as specified


Input: [Name] align-content [Value] flex-start | flex-end | center | space-between | space-around | stretch [Initial] stretch [Applies to] multi-line flex containers [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: specified value


Input: [Id: Title] litani1 : Document-editing interfaces description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] litani2 : Active grammar references [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] litani3 : Missing contentType constants [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] litani4 : wfValidityCheckLevel parameter should be added [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani5 : Add canWrap() convenience method [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani6 : Add getNextSiblings/getPreviousSiblings convenience methods [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani7 : Add getAlternativeElements method [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani8 : Add getRequiredAttributes method [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani9 : Add methods to retrieve enumerated and default values [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani10 : Change NodeList return types to list of QNames [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] litani11 : Remove getParentElements method [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] ausbrooks1 : More stringent validation for some XML dialects [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt1 : NO_GRAMMAR_AVAILABLE [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt2 : contentType [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt3 : allowedChildren [State] agreed [Ack.] No reply from reviewer [Type]

Output: proposal


Input: [Id: Title] curt4 : requiredAttributes [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt5 : NameList [State] subsumed [curt22] [Type]

Output: proposal


Input: [Id: Title] curt6 : External grammars [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt7 : Separation of Validation features [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt8 : Exceptions on setting continousValidityChecking [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt9 : RangeVAL [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt10 : VAL-DOC [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt11 : continuousValidityChecking typo [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt12 : continuousValidityChecking description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt13 : getDefinedElements description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt14 : validateDocument description [State] agreed [Ack.] No reply from reviewer [Type]

Output: editorial


Input: [Id: Title] curt15 : isNodeValid typo [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt16 : allowedChildren description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt17 : canSetAttributeNS qualifiedName parameter [State] declined [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt18 : canSetAttributeNode description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] curt19 : contentType values [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt20 : isElementDefined and isElementDefinedNS [State] declined [Ack.] No reply from reviewer [Type]

Output: proposal


Input: [Id: Title] curt21 : canDeleteData, canReplaceData, canInsertData exceptions [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] curt22 : NameList link [State] moved [Ack.] No reply from reviewer [Type]

Output: editorial


Input: [Id: Title] lmartin1 : Editorial comments [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin2 : Grammar definition [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin3 : Binding schemas to documents [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin4 : Partial validity rewrite [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin5 : Alternative term/definition for partial validity [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin6 : continuousValidityChecking description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin7 : continuousValidityChecking further clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin8 : Rename getDefinedElementTypes [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin9 : getDefinedElements description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin10 : validateDocument description [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin11 : Description of error handler for validateDocument [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin12 : Different validation outcomes [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin13 : isNodeValid definition [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin14 : Different outcomes [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin15 : canAppendChild description typo [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin16 : enumeratedValues description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin17 : NodeEditVAL interface to extend Node? [State] declined [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin18 : can* methods to throw exception if no grammar [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin19 : Discussion of wildcards for allowed* methods [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] lmartin20 : isElementDefined description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin21 : isElementDefinedNS description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin22 : SIMPLE_CONTENTTYPE description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin23 : ANY_CONTENTTYPE description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Id: Title] lmartin24 : isWhiteSpaceOnly description clarification [State] agreed [Ack.] Agreement [Type]

Output: editorial


Input: [Semantics] The Party is the issuer of the policy statement [Comment] Must be supported. [Identifier]

Output: assigner

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party is the recipient of the policy statement [Comment] Must be supported. [Identifier]

Output: assignee

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party to be attributed [Comment] May be specified as part of the attribute action. [Identifier]

Output: attributedParty

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party to obtain consent from [Comment] May be specified as part of the obtainConsent action. [Identifier]

Output: consentingParty

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party to be informed of all uses [Comment] May be specified as part of the inform action. [Identifier]

Output: informedParty

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party is the recipient of the compensation [Comment] May be specified as part of the compensate duty action. [Identifier]

Output: compensatedParty

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party is the usage tracker [Comment] May be specified as part of the acceptTracking action. [Identifier]

Output: trackingParty

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Name] flex-direction [Value] row | row-reverse | column | column-reverse [Initial] row [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: no


Input: [Name] flex-wrap [Value] nowrap | wrap | wrap-reverse [Initial] nowrap [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: no


Input: [Name] flex-flow [Value] || [Initial] see individual properties [Applies to] see individual properties [Inh.] see individual properties [%ages] see individual properties [Media] see individual properties [Computed value] see individual properties [Animatable]

Output: see individual properties


Input: [Name] order [Initial] 0 [Applies to] flex items and absolutely-positioned children of flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: yes


Input: [Name] flex [Value] none | [ <‘flex-grow’> <‘flex-shrink’>? || <‘flex-basis’> ] [Initial] see individual properties [Applies to] flex items [Inh.] see individual properties [%ages] n/a [Media] visual [Canonical order] per grammar [Computed value] see individual properties [Animatable]

Output: no


Input: [Name] flex-grow [Initial] 0 [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: yes


Input: [Name] flex-shrink [Initial] 1 [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: yes


Input: [Name] flex-basis [Value] content | <‘width’> [Initial] auto [Applies to] flex items [Inh.] no [%ages] relative to the flex container’s inner main size [Media] visual [Computed value] as specified, with lengths made absolute [Animatable]

Output: as width


Input: [Name] justify-content [Value] flex-start | flex-end | center | space-between | space-around [Initial] flex-start [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: no


Input: [Name] align-items [Value] flex-start | flex-end | center | baseline | stretch [Initial] stretch [Applies to] flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: no


Input: [Name] align-self [Value] auto | flex-start | flex-end | center | baseline | stretch [Initial] auto [Applies to] flex items [Inh.] no [%ages] n/a [Media] visual [Computed value] auto computes to parent’s align-items value; otherwise as specified [Animatable]

Output: no


Input: [Name] align-content [Value] flex-start | flex-end | center | space-between | space-around | stretch [Initial] stretch [Applies to] multi-line flex containers [Inh.] no [%ages] n/a [Media] visual [Computed value] specified value [Animatable]

Output: no


Input: [QName Local Name] Success [Description] The operation succeeded. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] VersionMismatch [Description] The service does not support the protocol version specified in the request. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Sender [Description] An error occurred that was due to the message sent by the sender. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Represent [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [Name] ServiceDescription [Definition ref] section 4.3 Provenance query service discovery [Description]

Output: Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments.


Input: [Name] DirectQueryService [Definition ref] section 4.1.1 Direct HTTP query service description [Description]

Output: Type for a direct HTTP query service description. Mainly for use in RDF provenance query service descriptions, to distinguish direct HTTP query service descriptions from other query service descriptions.


Input: [Name] has_anchor [Definition ref] section 3.2 Resource represented as HTML , section 3.3 Resource represented as RDF [Description]

Output: Indicates a target-URI for an resource, used by an associated provenance record.


Input: [Name] has_provenance [Definition ref] section 3.1 Resource accessed by HTTP , section 3.2 Resource represented as HTML [Description]

Output: Indicates a provenance-URI for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource.


Input: [Name] has_query_service [Definition ref] section 3.1.1 Specifying Provenance Query Services [Description]

Output: Indicates a provenance query service that can access provenance related to its subject or anchor resource.


Input: [Name] describesService [Definition ref] section 4.1 Provenance query service description [Description]

Output: relates a generic provenance query service resource (type prov:ServiceDescription ) to a specific query service description (e.g. a prov:DirectQueryService or a sd:Service ).


Input: [Name] provenanceUriTemplate [Definition ref] section 4.1.1 Direct HTTP query service description [Description]

Output: Indicates a URI template string for constructing provenance-URIs


Input: [Name] pingback [Definition ref] section 5. Forward provenance Provenance pingback [Description]

Output: Relates a resource to a provenance pingback service that may receive forward additional provenance links about the resource.


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

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


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

Output: PCDATA


Input: [Requirement Name] R-CsvValidation [Definition] Ability to validate a CSV for conformance with a specified metadata definition [Davide's Comments] "This requirement is also related to R-ExternalDataDefinitionResource, but it adds to the functional part." [Eric's Comments] Recommend Acceptance [Jeremy's Comments]

Output: Accept

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToRdfTransformation [Definition] Ability to automatically transform a CSV into RDF [Eric's Comments] Recommend removing. Is this perhaps a best practice as opposed to a requirement? [Jeremy's Comments]

Output: Retain this requirement - this underpins the function to be able to transform CSV into a different encoding

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToJsonTransformation [Definition] Ability to automatically transform a CSV into JSON [Eric's Comments] Recommend removing. Is this perhaps a best practice as opposed to a requirement? [Jeremy's Comments]

Output: Retain this requirement - this underpins the function to be able to transform CSV into a different encoding

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CsvToXmlTransformation [Definition] Ability to transform a CSV into XML [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments]

Output: New

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CanonicalMappingInLieuOfAnnotation [Definition] Ability to transform CSV conforming to the core tabular data model yet lacking further annotation into a object / object graph serialisation [Eric's Comments] "This seems to be related to R-CsvToRdfTransformation, R-CsvToJsonTransformation. If these two are kept does this requirement go away?" [Jeremy's Comments]

Output: "This is intended to fulfil the requirement to transform a CSV file (to RDF, JSON or other!) when there is no additional metadata annotation available ... retain this requirement"

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-IndependentMetadataPublication [Definition] Ability to publish metadata independently from the tabular data resource it describes. [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments]

Output: New

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-SpecificationOfPropertyValuePairForEachRow [Definition] Ability to define a property-value pair for inclusion in each row. [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments]

Output: New

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-ConditionalProcessingBasedOnCellValues [Definition] Ability to apply conditional processing based on the value of a specific cell. [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments]

Output: New

Requirements analysis - CSV on the Web Working Group Wiki


Input: [Requirement Name] R-CommentLines [Definition] Ability to identify comment lines within a CSV file and skip over them during parsing, format conversion or other processing. [Davide's Comments] New [Eric's Comments] New [Jeremy's Comments]

Output: New

Requirements analysis - CSV on the Web Working Group Wiki


Input: [RFC Property] CATEGORIES [Note] The categories of the object [N-Ary Property] hasCategory [Ontology Property]

Output: category

vCard Ontology - for describing People and Organizations


Input: [RFC Property] NOTE [Note] Notes about the object [N-Ary Property] hasNote [Ontology Property]

Output: note

vCard Ontology - for describing People and Organizations


Input: [RFC Property] PRODID [Note] The identifier of the product that created the vCard object [Ontology Property]

Output: prodid

vCard Ontology - for describing People and Organizations


Input: [RFC Property] REV [Note] The revision datetime of the vCard object [Ontology Property]

Output: rev

vCard Ontology - for describing People and Organizations


Input: [RFC Property] SOUND [Note] Audio related to the object (data URI) [Ontology Property]

Output: hasSound

vCard Ontology - for describing People and Organizations


Input: [RFC Property] UID [Note] A unique identifier for the object [Ontology Property]

Output: hasUID

vCard Ontology - for describing People and Organizations


Input: [RFC Property] URL [Note] Any URL related to the object [Ontology Property]

Output: hasURL

vCard Ontology - for describing People and Organizations


Input: [Identifier] absolutePosition [Comment] For example, JPEG image must be positioned at 100×100 pixel location. This may be used to express [PLUS] semantics. [Semantics]

Output: A point defined with absolute coordinates

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.3.1: Terms for the attribute “name” of the entity Constraint


Input: [Identifier] absoluteSize [Comment] For example, JPEG image must be reproduced onto an area no larger than A0. This may be used to express [PLUS] semantics. [Semantics]

Output: The absolute dimension that the Asset may be resized

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] count [Comment] Should be a positive integer. [Semantics]

Output: The numeric count indicating the number of times the corresponding entity may be exercised

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] dateTime [Comment] Date and Time value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. The use of Timezone information is strongly recommended. [Semantics]

Output: The date (and optional time and timezone) representing a point in time or period

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] fileFormat [Comment] For example, this may be used to express [PLUS] semantics; only JPEG image may be distributed. [Semantics]

Output: The file format applicable to the Asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] industry [Comment] For example, publishing, financial. [Semantics]

Output: The defined industry sector applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] language [Comment] For example, this may be used to express [PLUS] semantics; JPEG image may only be reproduced with Spanish text. Must use [BCP-47] codes. [Semantics]

Output: The natural language applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] deliveryChannel [Comment] For example, the asset may be distributed only on mobile networks. [Semantics]

Output: The delivery channel used for storing or communicating the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] elapsedTime [Comment] The start of the period is when the action is first exercised. [Semantics]

Output: A period of time in which the policy action can be exercised.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] event [Comment] For example, asset may be used at the “FIFA World Cup” only. To express events related to undertaking Duties, a specific event value has been defined: policyUsage – the time period whilst the policy is being exercised This will enable constraints to be expressed such as “event lt o:policyUsage” indicating before the policy is exercised. [Semantics]

Output: Specification of a defined event applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] media [Comment] For example, electronic, print, advertising, marketing. This may be used to express [PLUS] semantics. [Semantics]

Output: The media type in which the asset may be used

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] meteredTime [Comment] Value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example “P30H” indicates a 30 hour period. [Semantics]

Output: The maximum period of metered usage time

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] payAmount [Comment] The dataType attribute may be used to indicate the type of the value (eg decimal) and the unit attribute to indicate the currency. May be used for compensation duties. [Semantics]

Output: The value of the financial payment

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] percentage [Comment] A numeric value from 0 to 100. For example, extract a maximum of 50% of the asset [Semantics]

Output: The amount (as a percentage) of the action applicable to the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] product [Comment] For example, this may be used to express [PLUS] semantics; images may only be reproduced in the XYZ Magazine. [Semantics]

Output: The specified Product or Service name

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] purpose [Comment] For example, educational use. [P3P] Purpose values may also be used. [Semantics]

Output: Specification of a defined purpose applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] recipient [Comment] The right operand must identify one or more specific parties or categories of party [Semantics]

Output: The party that receives the result of the Action on the Asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] relativePosition [Comment] For example, this may be used to express [PLUS] semantics; JPEG image must be positioned at the Top of the Page. [Semantics]

Output: A point defined with reference to another position

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] relativeSize [Comment] For example, this may be used to express [PLUS] semantics; JPEG image resized to maximum of 200%. [Semantics]

Output: The relative dimension that the Asset may be resized

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] resolution [Comment] For example, may be printed at 1200dpi. [Semantics]

Output: The resolution at which the asset may be used

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] spatial [Comment] The code value and code source must be represented. For example, the ISO-3166 Country Codes and the Getty Thesaurus of Geographic Names. A URI should be used to represent this value. [Semantics]

Output: A code representing a geospatial area

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] timeInterval [Comment] Interval value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example, “P7D” indicates a 7 day period. [Semantics]

Output: Recurring period of time in which the usage may be exercised

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] systemDevice [Comment] For example, identifiable via the CPU or unique hardware address. [Semantics]

Output: An identifiable computing system

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] version [Comment] For example, Single Paperback, or Multiple Issues. This may be used to express [PLUS] semantics. [Semantics]

Output: The scope of versions for the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] virtualLocation [Comment] For example, an Internet domain or IP address range [Semantics]

Output: Specification of a digital locale

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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: [Name] event [Required] false [Attribute Constraints] Must not occur with 'eventexpr'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'eventexpr' must be present. [Default Value] none [Description] A string indicating the name of message being generated. See E Schema for details on the data type. [Type]

Output: EventType.datatype

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


Input: [Name] eventexpr [Required] false [Attribute Constraints] Must not occur with 'event'. If the type is http://www.w3.org/TR/scxml/#SCXMLEventProcessor, either this attribute or 'event' must be present. [Default Value] none [Description] A dynamic alternative to 'event'. If this attribute is present, the SCXML Processor MUST evaluate it when the parent element is evaluated and treat the result as if it had been entered as the value of 'event'. [Type]

Output: Value expression

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


Input: [Name] target [Required] false [Attribute Constraints] Must not occur with 'targetexpr' [Default Value] none [Valid Values] A valid target URI [Description] The unique identifier of the message target that the platform should send the event to. See 6.2.4 The Target of Send for details. [Type]

Output: URI

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


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

Output: Value expression

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


Input: [Name] type [Required] false [Attribute Constraints] Must not occur with 'typeexpr' [Default Value] none [Description] The URI that identifies the transport mechanism for the message. See 6.2.5 The Type of Send for details. [Type]

Output: URI

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


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

Output: value expression

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


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

Output: xml:ID

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


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

Output: Location expression

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


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

Output: Duration.datatype

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


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

Output: Value expression

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


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

Output: List of location expressions

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


Input: [Major Concepts] Service AtomicProcess composedOf message channel [Module]

Output: FLOWS-Core

The FLOWS Process Model Ontology Modules


Input: [Major Concepts] Split Sequence Unordered Choice IfThenElse Iterate RepeatUntil [Module]

Output: Control Constraints


Input: [Major Concepts] OrderedActivity [Module]

Output: Ordering Constraints


Input: [Major Concepts] OccActivity [Module]

Output: Occurrence Constraints


Input: [Major Concepts] TriggeredActivity [Module]

Output: State Constraints


Input: [Major Concepts] Exception [Module]

Output: Exception Constraints


Input: [Attribute Type] CDATA [Definition]

Output: Character data

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] IDREFS [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data

Modularization of XHTML - Defining Abstract Modules


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: ID

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: IDREF

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: IDREFS

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: NAME

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: NMTOKEN

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: NMTOKENS

XHTML Modularization 1.1 - Defining Abstract Modules


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

Output: No conflict

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict

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


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

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

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


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

Output: No conflict

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


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

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

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


Input: [Event Type] cancel [Action] don’t reprompt [Audio Provided]

Output: no

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] error [Action] exit interpreter [Audio Provided]

Output: yes

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] exit [Action] exit interpreter [Audio Provided]

Output: no

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] help [Action] reprompt [Audio Provided]

Output: yes

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] noinput [Action] reprompt [Audio Provided]

Output: no

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] nomatch [Action] reprompt [Audio Provided]

Output: yes

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] telephone.disconnect [Action] exit interpreter [Audio Provided]

Output: no

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Event Type] all others [Action] exit interpreter [Audio Provided]

Output: yes

Voice eXtensible Markup Language (VoiceXML) version 1.0


Input: [Test Name] animate-elem-02-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-03-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-04-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-05-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-06-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-07-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-08-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-09-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-10-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-11-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-12-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-13-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-14-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-15-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-16-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-17-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-18-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-19-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-20-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-21-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-22-b [ASV6p1] Ok [Batik] Fail [CSIRO Full] Partial [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-23-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-24-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-25-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-26-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-27-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-28-t [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] animate-elem-29-b [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] color-prof-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] color-prop-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] color-prop-02-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] color-prop-03-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-02-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-03-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-04-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-05-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-trans-06-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-units-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Partial [LXViewer08] Partial [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Partial [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-units-02-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-units-03-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Partial [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-viewattr-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] coords-viewattr-02-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Unknown [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] extend-namespace-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-blend-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-color-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-composite-02-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-comptran-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-conv-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-diffuse-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-displace-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-example-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-gauss-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-image-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-light-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-morph-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-offset-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-specular-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-tile-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] filters-turb-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] fonts-elem-01-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] fonts-elem-02-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] fonts-elem-03-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Fail [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] fonts-elem-04-b [ASV6p1] Ok [Batik] Fail [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Fail [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-cursor-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Partial [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-dom-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-events-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-order-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-order-02-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Partial [LXViewer08] Ok [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-order-03-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Partial [LXViewer08] Partial [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] interact-zoom-01-t [ASV6p1] Ok [Batik] Partial [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-a-01-b [ASV6p1] Fail [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Fail [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-a-02-b [ASV6p1] Fail [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Fail [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-a-03-b [ASV6p1] Fail [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Fail [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-a-04-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-uri-01-b [ASV6p1] Partial [Batik] Ok [CSIRO Full] Partial [LXViewer08] Fail [ASV3] Partial [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-uri-02-b [ASV6p1] Fail [Batik] Ok [CSIRO Full] Partial [LXViewer08] Fail [ASV3] Fail [CSV] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] linking-uri-03-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-mask-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-opacity-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-path-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-path-02-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-path-03-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-path-04-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] masking-path-05-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] metadata-example-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-fill-01-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-fill-02-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-fill-03-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-fill-04-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-marker-01-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-marker-02-f [ASV6p1] Ok [Batik] Ok [CSIRO Full] Fail [LXViewer08] Partial [ASV3] Ok [CSV] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Partial [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-render-01-b [ASV6p1] Ok [Batik] Ok [CSIRO Full] Partial [LXViewer08] Fail [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-stroke-01-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-stroke-02-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-stroke-03-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Partial [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Partial [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] painting-stroke-04-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] paths-data-01-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] paths-data-02-t [ASV6p1] Ok [Batik] Ok [CSIRO Full] Ok [LXViewer08] Ok [ASV3] Ok [CSV] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [Amaya-81a-GL]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status