SVG Working Group Charter

The mission of the SVG Working Group, part of the Graphics Activity, is to continue the evolution of Scalable Vector Graphics as a format and a platform, and enhance the adoption and usability of SVG in combination with other technologies.

Join the SVG Working Group.

End date 30 April 2012
Confidentiality Proceedings are public
Initial Chairs Erik Dahlström, Cameron McCormack
Initial Team Contacts
(FTE %: 100)
Doug Schepers, Chris Lilley
Usual Meeting Schedule Teleconferences: Twice Weekly
Face-to-face: 3-4 per year


SVG has matured into a widely-implemented specification for interactive graphics, used in viewers, authoring tools, and other standards. The SVG Working Group needs to build upon this solid foundation by adding new graphical and behavioral features to make it even easier for content creators to make compelling and effective graphical content. This includes syntactic sugar and canned effects for some of its more powerful features such as filters and animation. It is important for SVG to maintain a minimum degree of backwards compatibility with existing implementations.

Since SVG is also used as part of a platform for rich Web applications, both alone and in conjunction with other technologies such as HTML, the SVG Working Group must address the needs of those developers. Since the SVG language was originally developed at a time without the broad proliferation of different browsers under active development, and when many basic architectural aspects of XML were still developing, some features of the SVG language were not ideally integrated into other languages and architectural design. Specifically, SVG's DOM APIs and certain syntactic conventions need reexamination and redesign. The SVG Working group intends to solicit community feedback from known experts in addressing these issues, perhaps through a workshop.

Many features of SVG were successful enough to be adopted by CSS, such as gradients, filter effects, and animations, and in order to ensure interoperability, the SVG Working Group must work closely with the CSS Working Group to co-develop those features, to provide a consistent model for authors and implementers.

The Canvas API provides a complementary method for creating dynamic raster graphics, and the use of this API in SVG will provide more power for authors. A shared graphical API for both SVG and Canvas may be appropriate.

SVG will benefit from more explicit integration with other technologies such as X/HTML, as outlined in specifications produced by the CDF and HTML Working Groups, styling and layout technologies produced by the CSS and XSL-FO Working Groups, and more precise measures for accessibility.

For all new work, the SVG Working Group intends to gather and publish produce use cases and requirements, primers to illustrate the purpose and use of specifications, test suites to ensure interoperable implementations, and where possible, script libraries to prototype features and allow for early experimentation and adoption by authors.

In addition, the SVG Working Group will continue to maintain existing SVG specifications, publish errata and new revisions where required, update test suites, and provide current implementation reports.

Success Criteria

Out of Scope

There are several technologies closely related to SVG, but which are under the purview of other activities within W3C, and are detailed under Dependencies and Liaisons.


The working group will deliver at least the following:

Recommendation-Track Deliverables

Other Deliverables

  • Comprehensive implementation test suite for each specification
  • Implementation and interoperability reports (if resources are available)
  • Validation tools through collaboration with W3C Team
  • Updated Accessibility Note
  • Tutorial or primer resources (in conjunction with SVG Interest Group)
  • Reviews of other specifications that impact SVG


Specification transition estimates and other milestones.

Deliverable Milestones
Note: The group will document significant changes from this initial schedule on the group home page.
Specification FPWD LC CR PR Rec
Animation and Media
Color Management October 2009 September 2010 November 2010 May 2011 July 2011
Compositing February 2008 March 2010 May 2010 August 2010 September 2010
Connectors January 2010 September 2010 November 2010 May 2011 July 2011
Filters May 2007 September 2010 November 2010 May 2011 July 2011
Integration December 2009 September 2010 November 2010 January 2011 March 2011
Layout Requirements and Use Cases May 2008 June 2010
Layout July 2010 October 2010 December 2010 June 2011 August 2011
Masking and Clipping July 2008 March 2010 May 2010 August 2010 September 2010
Media Access Events October 2006 March 2010 May 2010 August 2010 September 2010
Pagination May 2010 December 2010 March 2011 October 2011 December 2011
Paint Servers April 2009 September 2010 November 2010 May 2011 July 2011
Parameters April 2009 August 2010 October 2010 May 2011 July 2011
Transformations March 2009 July 2010 October 2010 May 2011 July 2011
Vector Effects September 2008 September 2010 November 2010 May 2011 July 2011
SVG 2.0 April 2010 April 2011 July 2011 December 2011 June 2012
SVG Fonts moved to Fonts WG?

Timeline View Summary

  • Compositing: May 2009
  • Filters: February 2009
  • Layout Requirements and Use Cases: September 2008
  • Layout: February 2010
  • Masking and Clipping: July 2009
  • Media Access Events: December 2008
  • Paint Servers: June 2009
  • Print: December 2008
  • Vector Effects: December 2009
  • WebFonts: July 2009
  • SVG 1.1 Full 2nd Edition: March 2008
  • SVG 1.2 Tiny: October 2008
  • SVG 1.2 Full Modular: June 2010

Dependencies and Liaisons


Coordinate on styling and device aware adaption, collaborate on animation, layout, 2D and 3D transformations, in a joint Task Force.
Synchronized Multimedia (SYMM) Working Group
SVG uses SMIL Animation, audio and video, the 'switch' element, and the timing model from SMIL 2.1.
Web APps
The SVG WG has designed several APIs that supplement and extend DOM, and has asked the WebAPI WG to publish more generalized versions of them for use with all specifications; in addition, the SVG 1.2 Tiny specification has a dependency upon DOM3 Events, specifically the key and mousewheel events. Additionally, the SVG WG will strive to align its server communication methods with the XMLHttpRequest specification.
XML Core
SVG uses the XML, Namespaces in XML, XLink, and xml:id specifications.


Contribute to and follow the lead of the WICD specification to synergize SVG with other W3C languages to form a more effective whole solution for the Web.
Work closely with the HTML WG to provide integrated and consistent authoring experiences, and to explore how SVG can be used with HTML as well as XML-based languages like XHTML. In addition, form a joint task force with the HTML WG to specify the Canvas API, should the need arise.
WAI Protocols and Formats Working Group
Communicate about needs of accessibility in SVG UAs and language and extensibility features. Work with WAI to develop appropriate ontologies for the ARIA specificications.
Device Independence Activity
Meet the needs of a wide spectrum of devices.
Ubiquitous Web Applications
Integrate UWA WG specified criteria relevant to SVG, e.g. APIs exposing device capabilities.
MultiModal Architecture and Interfaces
Monitor MMI WG specifications for integration points, such as InkML.
Internationalization Activity
Ensure SVG meets needs for internationalized text and content adaption.
Work with OASIS Open Document Format Technical Committee to integrate SVG as a first-class object.
Coordinate on API and feature level with OpenVG specification.
Coordinate at the API and feature level with JSR-226, JSR-287 and JSR-290 specifications.
Ensure compatibility for mobile content formats.
Provide guidance for integration and compatible extension of SVG.


To be successful, the SVG Working Group is expected to have 10 or more active participants for its duration. Effective participation to SVG Working Group is expected to consume one work day per week for each participant; two days per week for editors. The SVG Working Group will allocate also the necessary resources for building Test Suites for each specification (some effort for which may also come from members of the SVG Interest Group Test Suite Task Force) and maintaining existing specifications (including publication of errata).

Each organization may have up to two participants in the SVG Working Group for purposes of technical discussion, issue resolution, voting, and other issues of process, but may additionally allocate any number of participants for dedicated tasks, such as creating or maintaining the test suites, or providing tutorial materials, subject to member review and approval.

Participants are reminded of the Good Standing requirements of the W3C Process.


Feedback to this group may be sent to the public mailing list www-svg@w3.org (archive), or submitted to the public issue tracking system available from the feedback page. This group will post minutes to, and primarily conduct its technical work on, the mailing list public-svg-wg@w3.org (public archive).

Information about the group, including news and links to specifications and membership, is available from the SVG WG Public page. Member-only information (contact details for face-to-face meetings, teleconferences, etc.) is available from the SVG WG Member page, and on the Member-only mailing list w3c-svg-wg@w3.org (member archive).

Decision Policy

As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.

This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.

Patent Policy

This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.

For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.

About this Charter

This charter for the SVG Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.

Please also see the previous charter for this group.

Doug Schepers <schepers@w3.org>, Chris Lilley <chris@w3.org>
$Revision: 1.1 $ of $Date: 2010/01/11 20:02:16 $

$Date: 2010/01/11 20:02:16 $