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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


Input: [Attribute Type] CDATA [Definition]

Output: Character data

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] IDREFS [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Property] additionalType (added) [Expected Type] URL [Description]

Output: An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax.

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


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

Output: A short description of the entry.

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


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

Output: URL of an image of the entry.

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


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

Output: The name of the entry.

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


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

Output: URL of the entry.

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


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

Output: A secondary title of the entry.

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


Input: [Property] inLanguage [Expected Type] Language [Description]

Output: The language of the content. Please use one of the language codes from the IETF BCP 47 standard.

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


Input: [Property] dateCreated [Expected Type] Date [Description]

Output: The date on which the content was created (in ISO 8601 date format).

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


Input: [Property] dateModified [Expected Type] Date [Description]

Output: The date on which the content was most recently modified (in ISO 8601 date format).

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


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

Output: The keywords/tags used to describe this content.

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


Input: [Property] provider [Expected Type] Person or Organization [Description]

Output: Specifies the person or organization that distributed the content.

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


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

Output: A set of links that can help a user understand and navigate a website hierarchy.

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


Input: [Property] relatedLink (or “seeAlso”) [Expected Type] URL [Description]

Output: A link related to this web page, for example to other related web pages.

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


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

Output: The identifier of the entry.

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


Input: [Property] isEntryOf [Expected Type] BiologicalDatabase [Description]

Output: Indicates the database to which the entry belongs.

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


Input: [Property] taxonID (or “taxon”) [Expected Type] Text [Description]

Output: The taxonomy identifier of the entry. Please use the NCBI Taxonomy ID.

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


Input: [Property] taxon (or “taxonID”) [Expected Type] BiologicalDatabaseEntry (or Text) [Description]

Output: The taxonomy information of the entry.

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


Input: [Property] seeAlso (or “relatedLink”) [Expected Type] BiologicalDatabaseEntry (or URL) [Description]

Output: Reference to another resource.

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


Input: [Property] background-color [Definition] Sets the background colour of the HTML element. [Description]

Output: There are several ways to indicate background-color, including RGB values and keywords. Most people use hexadecimal notation, a pound/hash symbol (#) followed by six characters. The first pair indicates the red levels, and the second and third indicate the green and blue levels respectively—#RRGGBB. Many colour picker tools will help you find the hexadecimal notation of a given colour. Pure red, for example would be #FF0000. Valid values include a color value, transparent, or inherit.

CSS background images - Web Education Community Group


Input: [Property] image [Definition] Indicates the path or URL of the background image. [Description]

Output: Set the background-image by showing the browser where to find the image, using the URL. For example; url(alert.png). Note that the path is prefaced with they keyword url and wrapped in parenthesis. This syntax is important to the browser understanding that you mean to indicate a location. Valid values include a URL, none, or inherit.

CSS background images - Web Education Community Group


Input: [Property] repeat [Definition] Indicates in which direction the background image should be tiled. [Description]

Output: Images can be tiled vertically, horizontally, or both, to fill the entire width or height of an HTML element. Use background-repeat to instruct the browser to repeat a background image. Valid values include repeat, repeat-x, repeat-y, and no-repeat.

CSS background images - Web Education Community Group


Input: [Property] attachment [Definition] Sets the behaviour of the background image when the user scrolls. [Description]

Output: Images can either scroll with their content, or stay fixed in place in the view screen. Valid values include scroll, fixed, and inherit.

CSS background images - Web Education Community Group


Input: [Property] position [Definition] Tells the browser where to position the background image. [Description]

Output: Images can be displayed anywhere within the borders of the HTML element on which they are applied. Use background-position to precisely place your images for visual effect and layering. There are many useful ways to indicate background position, keywords and numeric values. Keywords (such as top and bottom) are very useful and easy to read. Pixel values are very precise, but don’t adapt to changing heights and widths. Negative pixel values are useful when using CSS sprites, as you’ll find out later. When percentages and pixels are used, the starting point is always the top left corner of the HTML element, although the way image positioning works with pixels and percentages is rather different. Pixels always move the image a set number of pixels towards the bottom and right of the containing box (or towards the top and left if they are negative values), regardless of the size of the image and the containing box. Percentages on the other hand move the image a percentage of the difference between the containing box size, and the image size. If the image and the containing box are the same size, percentages won’t move the image at all. Valid values include length (generally in pixels), percentage (of the width of the element), and the keywords top, right, bottom, left, and center. Note that center can be used to indicate both vertical and horizontal center. Note also that you can mix percentages and pixels in rules, but not keywords and pixels or keywords and percentages.

CSS background images - Web Education Community Group


Input: [Property] background [Definition] The shorthand property that can be used to describe all the other properties in one line. [Description]

Output: Shorthand properties are very nifty indeed. Most developers use them to keep the CSS as lean as possible and group related properties. You can write a general rule using shorthand, and then override it as needed with specific properties. The properties should always be indicated in the same order, to allow browsers to easily interpret the intended styles: color url repeat attachment (very rarely used; may be omitted) horizontal-position vertical-position An example of this shorthand with all the properties used (except attachment) is as follows: background: green url(logo.gif) no-repeat left top;

CSS background images - Web Education Community Group


Input: [Value] copy: [Description]

Output: A duplicate of the source object will be dropped into the target.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] move: [Description]

Output: The source object will be removed from its current location and dropped into the target.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] link: [Description]

Output: A reference or shortcut to the dragged object will be created in the target object.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] execute: [Description]

Output: A function supported by the drop target is executed, using the drag source as an input.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] popup: [Description]

Output: There is a popup menu or dialog that allows the user to choose one of the drag operations (copy, move, link, execute) and any other drag functionality, such as cancel.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] none (default): [Description]

Output: No operation can be performed; effectively cancels the drag operation if an attempt is made to drop on this object. Ignored if combined with any other token value. e.g. 'none copy' is equivalent to a 'copy' value.

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


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

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Fail

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Partial [CSV]

Output: Partial

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Partial [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Partial [SVG# 0.3] Fail [CSV]

Output: Partial

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Partial

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Partial

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [CSV]

Output: Partial

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Fail [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Fail [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Partial [CSV]

Output: Partial

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Fail [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Partial [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Ok [SVG# 0.3] Partial [CSV]

Output: Ok

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 [Amaya-81a-GL] Fail [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

Output: Ok

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

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 [Amaya-81a-GL] Ok [Mozilla SVG GDI] Ok [SVG# 0.3] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


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

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Definition] Character data [Attribute Type]

Output: CDATA

Modularization of XHTML - Defining Abstract Modules


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

Output: ID

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREF

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREFS

Modularization of XHTML - Defining Abstract Modules


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

Output: NAME

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKEN

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKENS

Modularization of XHTML - Defining Abstract Modules


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

Output: PCDATA

Modularization of XHTML - 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

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 Container = GSP endpoint] No conflict; added LDP headers [LDP Container = 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 Container = GSP endpoint] No conflict; added LDP headers [LDP Container = 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 Container = GSP endpoint] Conflict [LDP Container = 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 Container = GSP endpoint] Conflict [LDP Container = 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 Container = GSP endpoint] No conflict [LDP Container = 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 Container = GSP endpoint] No conflict [LDP Container = 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: [Language feature] address element [Restrictions] If specified, role must be contentinfo (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: article role


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

Output: note role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


Input: [Language feature] header element [Restrictions] If specified, role must be banner (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


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

Output: listitem role


Input: [Language feature] ol element [Restrictions] Role must be either list, tree, or directory [Default implied ARIA semantic]

Output: list role


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

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either region, document, application, contentinfo (ARIA restricts usage of this role to one per page), main (ARIA restricts usage of this role to one per page), search, alert, dialog, alertdialog, status, or log [Default implied ARIA semantic]

Output: region role


Input: [Language feature] table element [Restrictions] Role must be either grid or treegrid [Default implied ARIA semantic]

Output: grid role


Input: [Language feature] ul element [Restrictions] Role must be either list or tree, or directory [Default implied ARIA semantic]

Output: list role


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

Output: document role


Input: [Variable] author email [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The email of the author who created the widget, corresponding to the author element's email attribute.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] author href [Type] URI [Default Value] null [Overridden by] Step 7 [Description]

Output: The URI associated with the author who created the widget, corresponding to the author element's href attribute.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] author name [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The name of the author who created the widget, corresponding to the text content of the author element.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] feature list [Type] List [Default Value] null [Overridden by] Step 7 [Description]

Output: A list of features that correspond to features that were requested, via feature elements, by the author and are supported by the user agent. Each item in the list corresponds to a feature element's name attribute, whether it is required, and any associated parameters.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] icons [Type] List of file entries [Default Value] null [Overridden by] Step 7, Step 9 [Description]

Output: The icons of the widget as they correspond to the default icons and to the occurrence of custom icons that are supported by the widget package.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] start file encoding [Type] String [Default Value] UTF-8 [Overridden by] Step 7 [Description]

Output: The character encoding of the custom start file, corresponding to the content element's charset attribute (if any).

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] start file content-type [Type] String [Default Value] text/html [Overridden by] Step 7 [Description]

Output: The media type of the start file, corresponding to the content element's type attribute or to a default start file.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] main config doc [Type] File entry [Default Value] null [Overridden by] Step 6 [Description]

Output: The file entry that is the configuration document for the widget package located at the root of the widget package.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] localized config doc [Type] File entry [Default Value] null [Overridden by] Step 6 [Description]

Output: The file entry that is the configuration document for the widget package.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget description [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The description given to the widget by the author, corresponding to the text content of the description element in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget height [Type] unsigned short [Default Value] null [Overridden by] Step 7 [Description]

Output: The widget's visual height, corresponding to the widget element's height attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget id [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The identifier, corresponding to the widget element's id attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget license [Type] Object [Default Value] null [Overridden by] Step 7 [Description]

Output: The software license assigned to the widget by the author, corresponding to the text content of the license element in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget name [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The widget's name, corresponding to the name element in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget short name [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The widget's alternative short name, corresponding to the name element's short attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] Variable [Type] Type [Default Value] Default Value [Overridden by] Overridden by [Description]

Output: Description

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget version [Type] String [Default Value] null [Overridden by] Step 7 [Description]

Output: The widget's version, corresponding to the widget element's version attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget width [Type] unsigned short [Default Value] null [Overridden by] Step 7 [Description]

Output: The widget's visual width, corresponding to the widget element's width attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget window modes [Type] List of strings [Default Value] floating [Overridden by] Step 7 [Description]

Output: The window mode that corresponds to the content element's viewmodes attribute in the configuration document.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] widget start file [Type] File entry [Default Value] null [Overridden by] Step 7, Step 8 [Description]

Output: The start file for the widget package, corresponding to either one of the default start files or the file identified by the content element's src attribute.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Variable] user agent's locales [Type] List of strings [Default Value] null [Overridden by] Step 5 [Description]

Output: The user agent's locales is a list of language tags that represent the end-user's preferred language and regional settings derived from the operating system or user agent.

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Definition] Sets the background colour of the HTML element. [Description] There are several ways to indicate background-color, including RGB values and keywords. Most people use hexadecimal notation, a pound/hash symbol (#) followed by six characters. The first pair indicates the red levels, and the second and third indicate the green and blue levels respectively—#RRGGBB. Many colour picker tools will help you find the hexadecimal notation of a given colour. Pure red, for example would be #FF0000. Valid values include a color value, transparent, or inherit. [Property]

Output: background-color

CSS background images - Web Education Community Group


Input: [Definition] Indicates the path or URL of the background image. [Description] Set the background-image by showing the browser where to find the image, using the URL. For example; url(alert.png). Note that the path is prefaced with they keyword url and wrapped in parenthesis. This syntax is important to the browser understanding that you mean to indicate a location. Valid values include a URL, none, or inherit. [Property]

Output: image

CSS background images - Web Education Community Group


Input: [Definition] Indicates in which direction the background image should be tiled. [Description] Images can be tiled vertically, horizontally, or both, to fill the entire width or height of an HTML element. Use background-repeat to instruct the browser to repeat a background image. Valid values include repeat, repeat-x, repeat-y, and no-repeat. [Property]

Output: repeat

CSS background images - Web Education Community Group


Input: [Definition] Sets the behaviour of the background image when the user scrolls. [Description] Images can either scroll with their content, or stay fixed in place in the view screen. Valid values include scroll, fixed, and inherit. [Property]

Output: attachment

CSS background images - Web Education Community Group


Input: [Definition] Tells the browser where to position the background image. [Description] Images can be displayed anywhere within the borders of the HTML element on which they are applied. Use background-position to precisely place your images for visual effect and layering. There are many useful ways to indicate background position, keywords and numeric values. Keywords (such as top and bottom) are very useful and easy to read. Pixel values are very precise, but don’t adapt to changing heights and widths. Negative pixel values are useful when using CSS sprites, as you’ll find out later. When percentages and pixels are used, the starting point is always the top left corner of the HTML element, although the way image positioning works with pixels and percentages is rather different. Pixels always move the image a set number of pixels towards the bottom and right of the containing box (or towards the top and left if they are negative values), regardless of the size of the image and the containing box. Percentages on the other hand move the image a percentage of the difference between the containing box size, and the image size. If the image and the containing box are the same size, percentages won’t move the image at all. Valid values include length (generally in pixels), percentage (of the width of the element), and the keywords top, right, bottom, left, and center. Note that center can be used to indicate both vertical and horizontal center. Note also that you can mix percentages and pixels in rules, but not keywords and pixels or keywords and percentages. [Property]

Output: position

CSS background images - Web Education Community Group


Input: [Definition] The shorthand property that can be used to describe all the other properties in one line. [Description] Shorthand properties are very nifty indeed. Most developers use them to keep the CSS as lean as possible and group related properties. You can write a general rule using shorthand, and then override it as needed with specific properties. The properties should always be indicated in the same order, to allow browsers to easily interpret the intended styles: color url repeat attachment (very rarely used; may be omitted) horizontal-position vertical-position An example of this shorthand with all the properties used (except attachment) is as follows: background: green url(logo.gif) no-repeat left top; [Property]

Output: background

CSS background images - Web Education Community Group


Input: [Property] background-color [Description] There are several ways to indicate background-color, including RGB values and keywords. Most people use hexadecimal notation, a pound/hash symbol (#) followed by six characters. The first pair indicates the red levels, and the second and third indicate the green and blue levels respectively—#RRGGBB. Many colour picker tools will help you find the hexadecimal notation of a given colour. Pure red, for example would be #FF0000. Valid values include a color value, transparent, or inherit. [Definition]

Output: Sets the background colour of the HTML element.

CSS background images - Web Education Community Group


Input: [Property] image [Description] Set the background-image by showing the browser where to find the image, using the URL. For example; url(alert.png). Note that the path is prefaced with they keyword url and wrapped in parenthesis. This syntax is important to the browser understanding that you mean to indicate a location. Valid values include a URL, none, or inherit. [Definition]

Output: Indicates the path or URL of the background image.

CSS background images - Web Education Community Group


Input: [Property] repeat [Description] Images can be tiled vertically, horizontally, or both, to fill the entire width or height of an HTML element. Use background-repeat to instruct the browser to repeat a background image. Valid values include repeat, repeat-x, repeat-y, and no-repeat. [Definition]

Output: Indicates in which direction the background image should be tiled.

CSS background images - Web Education Community Group


Input: [Property] attachment [Description] Images can either scroll with their content, or stay fixed in place in the view screen. Valid values include scroll, fixed, and inherit. [Definition]

Output: Sets the behaviour of the background image when the user scrolls.

CSS background images - Web Education Community Group


Input: [Property] position [Description] Images can be displayed anywhere within the borders of the HTML element on which they are applied. Use background-position to precisely place your images for visual effect and layering. There are many useful ways to indicate background position, keywords and numeric values. Keywords (such as top and bottom) are very useful and easy to read. Pixel values are very precise, but don’t adapt to changing heights and widths. Negative pixel values are useful when using CSS sprites, as you’ll find out later. When percentages and pixels are used, the starting point is always the top left corner of the HTML element, although the way image positioning works with pixels and percentages is rather different. Pixels always move the image a set number of pixels towards the bottom and right of the containing box (or towards the top and left if they are negative values), regardless of the size of the image and the containing box. Percentages on the other hand move the image a percentage of the difference between the containing box size, and the image size. If the image and the containing box are the same size, percentages won’t move the image at all. Valid values include length (generally in pixels), percentage (of the width of the element), and the keywords top, right, bottom, left, and center. Note that center can be used to indicate both vertical and horizontal center. Note also that you can mix percentages and pixels in rules, but not keywords and pixels or keywords and percentages. [Definition]

Output: Tells the browser where to position the background image.

CSS background images - Web Education Community Group


Input: [Property] background [Description] Shorthand properties are very nifty indeed. Most developers use them to keep the CSS as lean as possible and group related properties. You can write a general rule using shorthand, and then override it as needed with specific properties. The properties should always be indicated in the same order, to allow browsers to easily interpret the intended styles: color url repeat attachment (very rarely used; may be omitted) horizontal-position vertical-position An example of this shorthand with all the properties used (except attachment) is as follows: background: green url(logo.gif) no-repeat left top; [Definition]

Output: The shorthand property that can be used to describe all the other properties in one line.

CSS background images - Web Education Community Group


Input: [0] Standards Status [Transaction Layer Security] Same as XKMS Specification [WS-Security] Approved as an OASIS Technical Committee [Payload Security]

Output: Same as XKMS specification.

XML Key Management Specification (XKMS) Part II


Input: [0] Dependencies [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [WS-Security] Authentication mechanism defined by Web Services Infrastructure, is common to all Web Services. [Payload Security]

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

XML Key Management Specification (XKMS) Part II


Input: [0] Use of XML Signature [Transaction Layer Security] Not required [WS-Security] Uses XML Signature in Detached mode which slightly simplifies processing. [Payload Security]

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

XML Key Management Specification (XKMS) Part II


Input: [0] Support for Routing [Transaction Layer Security] None [WS-Security] Model is extensible to multi-hop message routing and multi-party transactions. [Payload Security]

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

XML Key Management Specification (XKMS) Part II


Input: [0] Support for Confidentiality [Transaction Layer Security] Supported [WS-Security] Confidentiality is supported through WS-Encryption [Payload Security]

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

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


Input: [Property] additionalType (added) [Expected Type] URL [Description]

Output: An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax.

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


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

Output: A short description of the entry.

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


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

Output: URL of an image of the entry.

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


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

Output: The name of the entry.

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


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

Output: URL of the entry.

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


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

Output: A secondary title of the entry.

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


Input: [Property] inLanguage [Expected Type] Language [Description]

Output: The language of the content. Please use one of the language codes from the IETF BCP 47 standard.

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


Input: [Property] dateCreated [Expected Type] Date [Description]

Output: The date on which the content was created (in ISO 8601 date format).

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


Input: [Property] dateModified [Expected Type] Date [Description]

Output: The date on which the content was most recently modified (in ISO 8601 date format).

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


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

Output: The keywords/tags used to describe this content.

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


Input: [Property] provider [Expected Type] Person or Organization [Description]

Output: Specifies the person or organization that distributed the content.

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


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

Output: A set of links that can help a user understand and navigate a website hierarchy.

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


Input: [Property] relatedLink (or “seeAlso”) [Expected Type] URL [Description]

Output: A link related to this web page, for example to other related web pages.

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


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

Output: The identifier of the entry.

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


Input: [Property] isEntryOf [Expected Type] BiologicalDatabase [Description]

Output: Indicates the database to which the entry belongs.

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


Input: [Property] taxonID (or “taxon”) [Expected Type] Text [Description]

Output: The taxonomy identifier of the entry. Please use the NCBI Taxonomy ID.

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


Input: [Property] taxon (or “taxonID”) [Expected Type] BiologicalDatabaseEntry (or Text) [Description]

Output: The taxonomy information of the entry.

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


Input: [Property] seeAlso (or “relatedLink”) [Expected Type] BiologicalDatabaseEntry (or URL) [Description]

Output: Reference to another resource.

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


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML Modularization 1.1 - Second Edition - Defining Abstract Modules


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

Output: ID

XHTML Modularization 1.1 - Second Edition - Defining Abstract Modules


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

Output: IDREF

XHTML Modularization 1.1 - Second Edition - Defining Abstract Modules


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

Output: IDREFS

XHTML Modularization 1.1 - Second Edition - Defining Abstract Modules


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

Output: NAME

XHTML Modularization 1.1 - Second Edition - 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 - Second Edition - Defining Abstract Modules


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

Output: NMTOKENS

XHTML Modularization 1.1 - Second Edition - Defining Abstract Modules


Input: [0] Standards Status [Payload Security] Same as XKMS specification. [Transaction Layer Security] Same as XKMS Specification [WS-Security]

Output: Approved as an OASIS Technical Committee

XML Key Management Specification (XKMS) Part II


Input: [0] Dependencies [Payload Security] Authentication defined by XKMS specification, client does not need to implement a comprehensive framework. [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [WS-Security]

Output: Authentication mechanism defined by Web Services Infrastructure, is common to all Web Services.

XML Key Management Specification (XKMS) Part II


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

Output: Uses XML Signature in Detached mode which slightly simplifies processing.

XML Key Management Specification (XKMS) Part II


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

Output: Model is extensible to multi-hop message routing and multi-party transactions.

XML Key Management Specification (XKMS) Part II


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

Output: Confidentiality is supported through WS-Encryption

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The email of the author who created the widget, corresponding to the author element's email attribute. [Variable]

Output: author email

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] URI [Default Value] null [Overridden by] Step 7 [Description] The URI associated with the author who created the widget, corresponding to the author element's href attribute. [Variable]

Output: author href

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The name of the author who created the widget, corresponding to the text content of the author element. [Variable]

Output: author name

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] List [Default Value] null [Overridden by] Step 7 [Description] A list of features that correspond to features that were requested, via feature elements, by the author and are supported by the user agent. Each item in the list corresponds to a feature element's name attribute, whether it is required, and any associated parameters. [Variable]

Output: feature list

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] List of file entries [Default Value] null [Overridden by] Step 7, Step 9 [Description] The icons of the widget as they correspond to the default icons and to the occurrence of custom icons that are supported by the widget package. [Variable]

Output: icons

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] UTF-8 [Overridden by] Step 7 [Description] The character encoding of the custom start file, corresponding to the content element's charset attribute (if any). [Variable]

Output: start file encoding

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] text/html [Overridden by] Step 7 [Description] The media type of the start file, corresponding to the content element's type attribute or to a default start file. [Variable]

Output: start file content-type

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] File entry [Default Value] null [Overridden by] Step 6 [Description] The file entry that is the configuration document for the widget package located at the root of the widget package. [Variable]

Output: main config doc

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] File entry [Default Value] null [Overridden by] Step 6 [Description] The file entry that is the configuration document for the widget package. [Variable]

Output: localized config doc

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The description given to the widget by the author, corresponding to the text content of the description element in the configuration document. [Variable]

Output: widget description

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] unsigned short [Default Value] null [Overridden by] Step 7 [Description] The widget's visual height, corresponding to the widget element's height attribute in the configuration document. [Variable]

Output: widget height

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The identifier, corresponding to the widget element's id attribute in the configuration document. [Variable]

Output: widget id

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] Object [Default Value] null [Overridden by] Step 7 [Description] The software license assigned to the widget by the author, corresponding to the text content of the license element in the configuration document. [Variable]

Output: widget license

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The widget's name, corresponding to the name element in the configuration document. [Variable]

Output: widget name

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The widget's alternative short name, corresponding to the name element's short attribute in the configuration document. [Variable]

Output: widget short name

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] Type [Default Value] Default Value [Overridden by] Overridden by [Description] Description [Variable]

Output: Variable

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] String [Default Value] null [Overridden by] Step 7 [Description] The widget's version, corresponding to the widget element's version attribute in the configuration document. [Variable]

Output: widget version

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] unsigned short [Default Value] null [Overridden by] Step 7 [Description] The widget's visual width, corresponding to the widget element's width attribute in the configuration document. [Variable]

Output: widget width

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] List of strings [Default Value] floating [Overridden by] Step 7 [Description] The window mode that corresponds to the content element's viewmodes attribute in the configuration document. [Variable]

Output: widget window modes

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] File entry [Default Value] null [Overridden by] Step 7, Step 8 [Description] The start file for the widget package, corresponding to either one of the default start files or the file identified by the content element's src attribute. [Variable]

Output: widget start file

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Type] List of strings [Default Value] null [Overridden by] Step 5 [Description] The user agent's locales is a list of language tags that represent the end-user's preferred language and regional settings derived from the operating system or user agent. [Variable]

Output: user agent's locales

Widgets 1.0: Packaging and Configuration

Configuration Defaults


Input: [Field] Title [Formal definition] dc:title [Description]

Output: The title of the publication.


Input: [Field] Author / Contributor [Formal definition] dc:creator + prism:role + foaf:Person [Description]

Output: Each individual that contributed to the publication. Individuals can be modeled as a foaf:Person in conjunction with the properties specified in the formal definition.


Input: [Field] Affiliation [Formal definition] swrc:affiliation [Description]

Output: The affiliation of each author. Can be modeled as foaf:Organization in conjunction with the properties specified in the formal definition.


Input: [Field] Publishing venue [Formal definition] prism:publicationName [Description]

Output: The publishing venue of the publication. Modeled in PRISM as publicationName: Title of the magazine, or other publication, in which a resource was/will be published


Input: [Field] Date [Formal definition] dc:date [Description]

Output: The publishing date of the publication.


Input: [Field] Abstract [Formal definition] dcterms:abstract [Description]

Output: The abstract of the publication


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

Output: Some

XML Key Management Specification (XKMS) Part II


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

Output: Some

XML Key Management Specification (XKMS) Part II


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

Output: Most

XML Key Management Specification (XKMS) Part II


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

Output: Some

XML Key Management Specification (XKMS) Part II


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

Output: All

XML Key Management Specification (XKMS) Part II


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

Output: Some

XML Key Management Specification (XKMS) Part II


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

Output: Most

XML Key Management Specification (XKMS) Part II


Input: [0] Standards Status [Payload Security] Same as XKMS specification. [WS-Security] Approved as an OASIS Technical Committee [Transaction Layer Security]

Output: Same as XKMS Specification

XML Key Management Specification (XKMS) Part II


Input: [0] Dependencies [Payload Security] Authentication defined by XKMS specification, client does not need to implement a comprehensive framework. [WS-Security] Authentication mechanism defined by Web Services Infrastructure, is common to all Web Services. [Transaction Layer Security]

Output: Authentication mechanism defined by TLS which clients must implement

XML Key Management Specification (XKMS) Part II


Input: [0] Use of XML Signature [Payload Security] Uses XML Signature in Enveloped Mode requiring slightly more complex processing. [WS-Security] Uses XML Signature in Detached mode which slightly simplifies processing. [Transaction Layer Security]

Output: Not required

XML Key Management Specification (XKMS) Part II


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

XML Key Management Specification (XKMS) Part II


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

Output: Supported

XML Key Management Specification (XKMS) Part II


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

Output: Requires additional payload security

XML Key Management Specification (XKMS) Part II


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

Output: Requires additional payload security

XML Key Management Specification (XKMS) Part II


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

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

XML Key Management Specification (XKMS) Part II


Input: [Entity Name] boxDL [Unicode/10646] 02557

Output: lower left quadrant BOX DRAWINGS DOUBLE DOWN AND LEFT

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxDl [Unicode/10646] 02556

Output: lower left quadrant BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxdL [Unicode/10646] 02555

Output: lower left quadrant BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxdl [Unicode/10646] 02510

Output: lower left quadrant BOX DRAWINGS LIGHT DOWN AND LEFT

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxDR [Unicode/10646] 02554

Output: lower right quadrant BOX DRAWINGS DOUBLE DOWN AND RIGHT

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxDr [Unicode/10646] 02553

Output: lower right quadrant BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxdR [Unicode/10646] 02552

Output: lower right quadrant BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxdr [Unicode/10646] 0250C

Output: lower right quadrant BOX DRAWINGS LIGHT DOWN AND RIGHT

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxH [Unicode/10646] 02550

Output: horizontal line BOX DRAWINGS DOUBLE HORIZONTAL

Character Description ISO Unicode/10646 Name


Input: [Entity Name] boxh [Unicode/10646] 02500

Output: horizontal line BOX DRAWINGS LIGHT HORIZONTAL

Character Description ISO Unicode/10646 Name