PROPOSED 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 June 2013
Confidentiality Proceedings are public
Initial Chairs Erik Dahlström, Cameron McCormack
Initial Team Contacts
(FTE %: 45)
Chris Lilley, Doug Schepers
Usual Meeting Schedule Teleconferences: One per week
Face-to-face: 2-3 per year


Scalable Vector Graphics has matured into a widely-implemented specification for interactive graphics, used in viewers, authoring tools, and other standards. The SVG Working Group will 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.

Since SVG is also used as part of a platform for rich Web applications, both alone and in combination with other technologies such as HTML, the SVG Working Group must address the needs of web application developers. In particular, the SVG Working Group will work with implementers and other experts to redesign the SVG DOM APIs and certain syntactic conventions, to make them simpler and more performant, and to integrate SVG more closely with other web languages, to improve use in gaming, multimedia experiences, and interactive data visualization. The group will also work with accessibility groups to define more precise measures for accessible info-graphics.

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 is working closely with the CSS Working Group to co-develop those features, to provide a consistent model for authors and implementers.

Many authors integrate SVG and HTML content, and this group will work with the HTML Working Group to improve that integration. In addition, the SVG Working Group may propose to work with the HTML WG to develop a shared graphical API for both SVG and the Canvas API, which could provide a complementary method for creating dynamic raster graphics.

For backwards compatibility with existing implementations and content, the group will provide a clear upgrade path from SVG 1.1 and SVG Tiny 1.2 to SVG 2. Some of the new functionality of SVG 2 may be defined in stand-alone modules which can be incrementally added to implementations of those earlier specifications. A modular approach may also help promote quick review and progress toward implementations and Recommendation status.

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

Each SVG specification will be considered successful if there are at least two independent, interoperable implementations of each normative assertion for features defined by the specification. The group will be considered successful if it progresses one or more of the deliverables to W3C Recommendation status.

Additional discretionary goals for the group include:

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 deliverables. Those specifications which may be joint deliverables with the CSS WG in the FX Task Force are marked with the two-colored circle symbol: . The deliverables are listed in rough order of priority, with the following supplementary color-coding: pale green for high priority, pale blue for medium priority, and pale red for low priority.

Recommendation-Track Deliverables

  • SVG 2 (high priority)
  • Filters (high priority)
  • Web Animation (high priority)
  • Compositing (high priority)
  • Integration (high priority)
  • Gradients (high priority)
  • Color Management (high priority)
  • Transformations
    • 2D Transforms (high priority)
    • 3D (Non-Affine, 2.5D) Transforms (medium priority)
  • Tiling and Layering (medium priority)
  • Parameters (medium priority)
  • Vector Effects (medium priority)
  • Accessibility (medium priority)
  • Graphics API (medium priority)
  • Pagination and Slides (low priority)
  • Connectors (low priority)
  • Layout (low priority)
  • SVG Fonts (low priority)
  • Media Access Events (low priority)

Other Deliverables

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


Timelines and milestones for the deliverables will be maintained on the group home page.

Dependencies and Liaisons


Coordinate on styling and device-aware adaptation, collaborate on animation, filters, layout, 2D and 3D transformations, and other topics in the joint Effects Task Force.


Work with the HTML WG to provide integrated and consistent authoring experiences, and to explore how SVG can be used with different serializations of HTML. In addition, this group may form a joint task force with the HTML WG to integrate the Canvas API for use in SVG.
The SVG WG intends to use the Web IDL specification as the formal language to define SVG interfaces. The SVG WG will also work with the WebApps WG to define new APIS and improvements to DOM.
WAI Protocols and Formats Working Group
Discuss needs of accessibility in SVG UAs and language and extensibility features. Work with WAI to develop appropriate ontologies for the ARIA specifications.
Device APIs and Policy Working Group
Integrate APIs exposing device capabilities.
Internationalization Activity
Ensure SVG meets needs for internationalized text and content adaptation.
Web Events
The SVG WG will work with the Web Events WG on events for actions such as zooming and panning.
Work with OASIS Open Document Format Technical Committee to integrate SVG as a first-class object.
Work with EPUB to facilitate reuse of SVG in electronic books.
Coordinate on APIs and features with OpenVG, OpenGL, and other specifications.
Provide guidance for integration and compatible extensions of SVG.


To be successful, the SVG Working Group is expected to have 6 or more active participants for its duration. Effective participation in the 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 and maintaining existing specifications (including publication of errata).

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 conducts technical discussions, including telcon minutes, on the public mailing list www-svg@w3.org. For logistics and other group information, the group maintains a public group-only mailing list, public-svg-wg@w3.org (public archive), and for Member-only information (e.g. personal contact details, etc.), maintains a Member-only mailing list w3c-svg-wg@w3.org (member archive).

Information about the group, including news and links to specifications and membership, is available from the SVG WG Public page.

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.

Chris Lilley <chris@w3.org>, Doug Schepers <schepers@w3.org>
$Revision: 1.9 $ of $Date: 2011/10/07 20:02:14 $

$Date: 2011/10/07 20:02:14 $