SVG is still evolving. What started as a technology largely developed and promoted by plugin implementers has now been natively implemented by most modern browsers, and is still in the process of being optimized for even closer integration with HTML and CSS in the browser. In addition, the SVG Tiny 1.2 specification was developed and deployed by mobile device vendors, with some features more appropriate for that platform than for the traditional browser.
The SVG Working Group has developed a plan to meet the needs of backwards compatibility and future growth of the language, based on the development of closely-tied modules. Each module will concentrate on one aspect of the language, defining and expanding the elements, attributes, script interfaces, methods, and other features specific to that subject (for example, color composition, filters, and parameters each have their own module).
Each module will be developed so that it can be independently integrated into SVG 1.1 or SVG Tiny 1.2 user agents, to expand each of those platforms. Each of these module specifications will be taken to Candidate Recommendation phase, where they will be "parked"... held for further implementation feedback, and refined with features and concepts shared in common with the other modules.
When each module is mature and the SVG WG is satisfied with the definitions, we will bundle them into a single specification, SVG 2.0, and publish them as individual module (for incremental implementation by existing user agents) and as a comprehensive SVG 2.0 specification that defines the state of the art for SVG.
The details of each module are outlined in the timeline below.
This is an updated Roadmap of all our work, with difference from our charter.
Note: though we try to keep this up-to-date, it may be that certain decisions or schedules may be overlooked (especially when we are very busy with a deadline). If you have any questions about this roadmap, please confirm the details by sending an email to the public SVG list, email@example.com.
|SVG 2.0||August 2012||March 2015||September 2016||June 2017||July 2017|
|SVG Integration||April 2014||December 2014||April 2015||June 2015||August 2015|
|Masking and Clipping||November 2012||October 2013||August 2014||July 2015||September 2015|
|Compositing||August 2012||January 2014||February 2014||July 2015||September 2015|
|CSS Animations||March 2009||July 2015||November 2015||August 2016||October 2016|
|CSS Transforms||February 2012||July 2015||November 2015||August 2016||October 2016|
|CSS Transitions||March 2009||July 2015||November 2015||August 2016||October 2016|
|Web Animations||June 2014||March 2015||July 2015||December 2015||February 2016|
|Geometry Interfaces||May 2014||March 2015||July 2015||December 2015||February 2016|
|Filter Effects||October 2012||April 2015||July 2015||March 2016||May 2016|
|SVG2 Accessibility API mapping||June 2015||January 2016||May 2016||October 2016||December 2016|
|SVG2 Accessible Authoring Guidelines||June 2015||January 2016||May 2016||October 2016||December 2016|
|SVG Parameters||April 2009||June 2015||December 2015||June 2016||August 2016|