This document uses the following definitions:
- Must: there is a consensus that the feature is essential
- Should: there is a consensus that the feature is good to have but may not be essential
1. Use Cases
USE 1. SVGT 1.2 must support progressively downloadable long cartoon animations.
USE 2. SVGT 1.2 must support controllable progressive rendering of large static content.
USE 3. SVGT 1.2 must support scalable, interactive maps.
USE 4. SVGT 1.2 must support scalable, animated icons.
USE 5. SVGT 1.2 must support multimedia content.
USE 6. SVGT 1.2 must support the ability to create visually compelling content.
USE 7. SVGT 1.2 should allow specification of a thumbnail of an SVG document.
USE 8. SVGT 1.2 must support game development.
USE 9. SVGT 1.2 must support simple user interfaces.
GEN 1. Two profiles are defined: SVG Tiny 1.2 ? Image,and SVG Tiny 1.2 ? Application. The profiles
must not contain
optional parts (i.e. all features must be implemented by all vendors) in order to claim compliance with a profile.
Changed. The Working Group tried to avoid optional parts, but was not able to do this in all cases. SVG Tiny 1.2 has a small number of optional parts. On the other hand, because of the uDOM, the number of mobile-friendly profiles could be reduced from two (in SVG 1.1) to one (in SVG 1.2).
GEN 2. SVGT 1.2 should clarify authoring guidelines for feature costs to content developers
Partly supported. The SVG Tiny 1.2 specification has a small amount of authoring guidance; a more comprehensive separate authoring guidelines document is planned.
GEN 3. SVGT 1.2 must develop at least 80 detailed conformance tests.
(This criterion applies to the CR period, and is expected to be met during that time)
ARCH 1. SVGT 1.2 must support a minimal API to control SVG content/animations compatible with other user agents, for the SVG Tiny Application profile.
Supported by the SVG Micro DOM (uDOM).
ARCH 2. SVGT 1.2 must support starting and stopping an audio clip.
Supported by the audio element.
ARCH 3. SVGT 1.2 must support switching between different audio formats
Supported by the audio element.
FUN 1. SVGT 1.2 should provide ability to provide hints to guide quality vs. speed for rendering text, shapes, and images (use case 1,2,3).
Supported by the rendering hint attributes.
FUN 2. SVGT 1.2 should support non-scaling objects (use case 3).
Supported by constrained transforms.
FUN 3. SVGT 1.2 must support non-scaling stroke (use case 3).
Supported by the non-scaling-stroke value of the vector-effect attribute.
4.2 Document Structure
FUN 4. SVGT 1.2 should support SVG content organized in pages (use case 1).
Unsupported. This functionality was explored and found to be unsuitable; pages (on the one hand) and timed scenes (on the other) are better represented using different constructs.
FUN 5. SVGT 1.2 should support rendering level of detail (use case 3).
FUN 6. SVGT 1.2 should support keyboard navigation - the specification of the navigation in a scene using keys.
Supported by Section 13.12 - Navigation.
FUN 7. SVGT 1.2 must support fill opacity.
Supportedby the fill-opacity attribute.
FUN 8. SVGT 1.2 must support stroke opacity.
Supported by the stroke-opacity attribute.
FUN 9. SVGT 1.2 must support subset of linear gradients (use case 1-5).
Supported by the linearGradient element.
FUN 10. SVGT 1.2 should support subset of radial gradients. (use case 1-4).
Supported by the radialGradient element.
FUN 11. SVGT 1.2 should support minimal text layout
Supported by the textArea element.
FUN 17. SVGT 1.2 should support tspan
Supported by the tspan element.
FUN 12. SVGT 1.2 should allow specification of a certain point in time for static rendering of an animation (e.g. for thumbnails) (use case 7).
Supported by the snapshotTime attribute of the svg element.
FUN 13. SVGT 1.2 should allow specification of a thumbnail of an SVG document (use case 7).
Supported by the snapshotTime attribute of the svg element. The size and format of the snapshot is not constrained by the SVG Tiny 1.2 specification.
FUN 14. SVGT 1.2 should support raster sprite animation.
Supported by the Section 16 - Animation
FUN 15. SVGT 1.2 must support interactivity (GEN.2).
Supported by Section 13 - Interactivity.
FUN 16. SVGT 1.2 Application must support scripting (DSM or DOM subset).
Supported by Section 15 - Scripting.
4.9 Coordinate Systems, Transformations and Units
FUN 18. SVGT 1.2 should support all align values for preserveAspectRatio attribute on image elements
Supported by the preserveAspectRatio attribute.