Scalable Vector Graphics (SVG) Tiny 1.2 Specification

Abstract

This specification defines the features and syntax for Scalable Vector Graphics (SVG) Tiny, Version 1.2, a language for describing two-dimensional vector and mixed vector/raster graphics in XML. Its goal is to provide the ability to create a whole range of graphical content, from static images to animations to interactive Web applications. SVG 1.2 Tiny is a profile of SVG intended for implementation on a range of devices, from cellphones and PDAs to desktop and laptop computers, and thus includes a subset of the features included in SVG 1.1 Full, along with new features to extend the capabilities of SVG. Further extensions are planned in the form of modules which will be compatible with SVG 1.2 Tiny, and which when combined with this specification, will match and exceed the capabilities of SVG 1.1 Full.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This is the 17 November 2008 Proposed Recommendation of SVG Tiny 1.2. The SVG Working Group plans to submit this specification for consideration as a W3C Recommendation, having demonstrated multiple interoperable implementations for each test in the SVG Tiny 1.2 test suite, with at least one of the passing implementations on a mobile platform. The SVG Working Group, working closely with the developer community, has produced an implementation report to prove the implementability of this specification. The Candidate Recommendation and Last Call Working Draft phases for this specification resulted in a number of comments which have been addressed by the SVG Working Group, with a Disposition of Comments available on the W3C SVG site. A partial list of changes made since the Last Call Working Draft is available in Appendix T. Because this specification had multiple interoperable implementations, and had previously been a Candidate Recommendation, the Director's decision was to advance directly to Proposed Recommendation. The Working Group does not plan to request to advance to Recommendation prior to 15 December 2008.

Please send questions or comments regarding the SVG 1.2 Tiny specification to www-svg@w3.org, the public email list for issues related to SVG. This list is archived and acceptance of this archiving policy is requested automatically upon first post. To subscribe to this list send an email to www-svg-request@w3.org with the word "subscribe" in the subject line.

Advisory Committee Representatives should respond to the WBS questionnaire with questions, comments or, support.

This document has been produced by the SVG Working Group as part of the W3C Graphics Activity, following the procedures set out for the W3C Process. The authors of this document are listed at the end in the Author List section.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

Available languages

The English version of this specification is the only normative version. However, for translations in other languages see https://www.w3.org/Graphics/SVG/svg-updates/translations.html.

Full Table of Contents

The authors of the SVG Tiny 1.2 specification are the people who participated in the SVG Working Group as members or alternates.

Authors:

• Ola Andersson, Ikivo
• Phil Armstrong, Corel Corporation
• Henric Axelsson, Ericsson AB
• Selim Balcısoy, Nokia
• Robin Berjon, Expway
• Benoît Bézaire, Itedo (formerly Corel Corporation)
• John Bowler, Microsoft Corporation
• Gordon Bowman, Corel Corporation
• Craig Brown, Canon Information Systems Research Australia
• Mike Bultrowicz, Savage Software
• Tolga Çapin, Nokia
• Milt Capsimalis, Autodesk Inc.
• Mathias Larsson Carlander, Ericsson AB
• Jakob Cederquist, Ikivo
• Suresh Chitturi, Nokia
• Charilaos Christopoulos, Ericsson AB
• Richard Cohn, Adobe Systems Inc.
• Lee Cole, Quark
• Cyril Concolato, Groupe des Ecoles des Télécommunications (GET)
• Don Cone, America Online Inc.
• Erik Dahlström, Opera Software (Working Group Chair)
• Alex Danilo, Canon Information Systems Research Australia
• Thomas DeWeese, Eastman Kodak
• David Dodds, Lexica
• Andrew Donoho, IBM
• David Duce, Oxford Brookes University
• Jean-Claude Dufourd, Streamezzo (formerly GET)
• Andrew Emmons, BitFlash (Working Group Chair)
• Jerry Evans, Sun Microsystems
• Jon Ferraiolo, Adobe Systems Inc.
• Darryl Fuller, Schema Software
• 藤沢 淳 (FUJISAWA Jun), Canon
• Scott Furman, Netscape Communications Corporation
• Brent Getlin, Macromedia
• Diego Gibellino, Telecom Italia
• Christophe Gillette, Motorola (formerly BitFlash)
• Peter Graffagnino, Apple
• Rick Graham, BitFlash
• Niklas Hagelroth, Ikivo
• Vincent Hardy, Sun Microsystems Inc.
• 端山 貴也 (HAYAMA Takanari), KDDI Research Labs
• Scott Hayman, Research In Motion Limited
• Stephane Heintz, OpenText (formerly BitFlash)
• Lofton Henderson, OASIS
• Ivan Herman, W3C
• Jan Christian Herlitz, Excosoft
• Anthony Grasso, Canon Information Systems Research Australia
• Alan Hester, Xerox Corporation
• Olaf Hoffmann, Invited Expert
• Bob Hopgood, RAL (CCLRC)
• Bin Hu, Motorola
• Michael Ingrassia, Nokia
• 石川 雅康 (ISHIKAWA Masayasu), W3C
• Dean Jackson, W3C (W3C Team Contact)
• Christophe Jolif, ILOG S.A.
• Lee Klosterman, Hewlett-Packard
• 小林 亜令 (KOBAYASHI Arei), KDDI Research Labs
• Thierry Kormann, ILOG S.A.
• Yuri Khramov, Schema Software
• Kelvin Lawrence, IBM
• Håkon Lie, Opera
• Chris Lilley, W3C (Working Group Chair)
• Vincent Mahe, France Telecom
• Philip Mansfield, Schema Software
• Lee Martineau, Quickoffice
• Charles McCathieNevile, Opera Software
• Kevin McCluskey, Netscape Communications Corporation
• Cameron McCormack, Invited Expert
• 水口 充 (MINAKUCHI Mitsuru), Sharp Corporation
• Luc Minnebo, Agfa-Gevaert N.V.
• Jean-Claude Moissinac, Groupe des Ecoles des Télécommunications (GET)
• Craig Northway, Canon Information Systems Research Australia
• Tuan Nguyen, Microsoft Corporation
• 小野 修一郎 (ONO Shuichiro), Sharp Corporation
• Lars Piepel, Vodafone
• Antoine Quint, Fuchsia Design (formerly ILOG)
• णन्दिनि ऱमनि (Nandini Ramani), Sun Microsystems
• Bruno David Simões Rodrigues, Vodafone
• 相良 毅 (SAGARA Takeshi), KDDI Research Labs
• Troy Sandal, Visio Corporation
• Peter Santangeli, Macromedia
• Doug Schepers, W3C (formerly Vectoreal) (W3C Team Contact)
• Sebastian Schnitzenbaumer, SAP AG
• Andrew Shellshear, Canon Inc.
• Haroon Sheikh, Corel Corporation
• Brad Sipes, Ikivo
• Andrew Sledd, Ikivo
• Пётр Соротокин (Peter Sorotokin), Adobe Systems Inc.
• Gavriel State, Corel Corporation
• Robert Stevahn, Hewlett-Packard
• Timothy Thompson, Eastman Kodak
• 上田 宏高 (UEDA Hirotaka), Sharp Corporation
• Rick Yardumian, Canon Development Americas
• Charles Ying, Openwave Systems Inc.
• Shenxue Zhou, Quark
• Atanas Zlatinski, Samsung Electronics

Acknowledgments

The SVG Working Group would like to acknowledge the many people outside of the SVG Working Group who help with the process of developing the SVG specification. These people are too numerous to list individually, but are greatly appreciated. They include but are not limited to the early implementers of the SVG languages (including viewers, authoring tools, and server-side transcoders), developers of SVG content, people who have contributed on the www-svg@w3.org and svg-developers@yahoogroups.com email lists, other Working Groups at the W3C, and the W3C Team. SVG is truly a cooperative effort between the SVG Working Group, the rest of the W3C, and the public, and benefits greatly from the pioneering work of early implementers and content developers, and from public feedback.