Please refer to the errata for this document, which may include some normative corrections.

This document is also available in these non-normative formats: a
single-page version
and a PDF.
See also translations, noting that the English version of this specification is the only normative version.

Abstract

This specification defines the features and syntax for Scalable
Vector Graphics (SVG) Version 1.1, a modularized language for describing
two-dimensional vector and mixed vector/raster graphics in XML.

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 http://www.w3.org/TR/.

This document is the 09 June 2011 Proposed Recommendation of the SVG 1.1
Second Edition specification. The Second Edition incorporates a
number of corrections that were published as
errata against the First Edition,
as well as numerous other changes that help make the specification
more readable and unambiguous. The Changes
appendix lists all of the changes that were made since the
first Last Call Working Draft publication of the Second Edition. For the changes made
between the First Edition and the Second Edition Working Draft,
see that
document's Changes appendix.

This specification moved from Last Call phase to Proposed Recommendation
phase without a Candidate Recommendation phase because of sufficient
implementation experience and wide interoperability.

Comments on this Proposed Recommendation are welcome. Please note however
that major corrections against the specification will be published as errata,
and subsequently will be incorporated into future editions of SVG 1.1 or into
SVG 2.0. Comments can be sent to www-svg@w3.org, the public email
list for issues related to vector graphics on the Web. This list is
archived and
senders must agree to have their message publicly archived from their
first posting. To subscribe send an email to www-svg-request@w3.org with
the word subscribe in the
subject line.

W3C Advisory Committee Members are invited to send formal review comments on this
Proposed Recommendation to the W3C Team until 07 July 2011.
Members of the W3C Advisory Committee will find the appropriate review form for this document by consulting their
list of current WBS questionnaires.

The W3C SVG Working Group has released an expanded
test suite for SVG 1.1
along with an
implementation report.
This test suite will continue to be updated with new tests to improve interoperability even after Recommendation phase.

A list of current W3C Recommendations and
other technical documents can be found at
http://www.w3.org/TR/. W3C publications
may be updated, replaced, or obsoleted by other documents at any time.

Publication as a Working Draft 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.

In addition, the SVG Working Group would like to acknowledge the
contributions of the editors and authors of
SVG 1.0 and
SVG 1.1 (First Edition),
as much of the text in this document derives from these earlier
versions of the SVG specification.

Finally, the SVG Working Group would like to acknowledge the
great many people outside of the SVG Working Group who help with the
process of developing the SVG specifications. These people are too
numerous to list individually. They include but are not limited to
the early implementers of the SVG 1.0 and 1.1 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 1.1 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, feedback from the public, and help from the W3C team.