The mission of the Scalable Vector Graphics (SVG) Working Group, part of the Graphics Activity of the Interaction Domain, 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.
|End date||31 Mar 2014|
|Confidentiality||Proceedings are public|
|Initial Chairs||Erik Dahlström (Opera),
Cameron McCormack (Mozilla)
|Initial Staff Contacts
(FTE %: 45)
|Usual Meeting Schedule||Teleconferences: Weekly
Face-to-face: 3-4 per year
The SVG WG develops the following technologies:
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 advanced gradients, 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. Besides improving interoperability and adding clarifications where necessary, the aims are also 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. The FX taskforce is the venue for this joint work.
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 will be defined in stand-alone modules which can be incrementally added to implementations of those earlier specifications. A modular approach is aimed at promoting quick review and progress toward implementations and Recommendation status.
In order to meet the specific needs of content creators using SVG for mapping applications, the SVG WG intends to form an SVG Mapping Task Force, to focus on use case and requirements, and to work on map-targeted modules such as the Tiling and Layering module. In addition, some of this functionality will benefit non-mapping applications such as high resolution photographic or medical imagery, so could be placed in the main SVG2 specification.
For all new work, the SVG Working Group intends to gather and publish 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.
The SVG Working Group's work is considered a success if there are multiple independent complete and interoperable implementations of its deliverables that are widely used.
Some modules are expected to become Recommendations in the timeframe of this charter. Others are expected to move to Candidate Recommendation and have test suites developed; or to move to Last Call.
These specifications have an active editor, an advocate in the Working group, are under active implementation and are expected to move to Recommendation status within two years.
Items jointly published by CSS and SVG WGs, such as those arising from the FX Task Force Work.
These modules have an editor, an advocate in the Working group, are expected to move to CR and have test suites developed within two years.
These modules may be worked on if there is time. They might not currently have an editor.
Items jointly published by I18n Core, CSS, XSL and SVG WGs
Maintenance items are W3C Recommendations (or are expected very soon to become Recommendations) which will be maintained by collecting errata and, if needed, by the publication of new editions incorporating those errata.
Completed items are finished, and not considered to require active maintenance.
The group creates a comprehensive test suite for each SVG specification before it becomes Recommendation.
The group monitors, tracks, and encourages implementation of SVG, both during Candidate Recommendation and afterwards.
Current status of each module, including implementation and testsuite status and other spec dependencies which may block it, is maintained on the SVG Roadmap page.
The following is a list of known liaisons with other W3C groups at the time this charter was written. The group also coordinates with groups not listed here through the Hypertext Coordination Group.
Furthermore, Scalable Vector Graphics (SVG) Working Group expects to follow these W3C Recommendations:
To be successful, The group is expected to have 7 or more active participants for its duration. Effective participation is expected to consume one work day per week for each participant; two days per week for editors. The group allocates also the necessary resources for building Test Suites.
Participants are reminded of the Good Standing requirements of the W3C Process.
The group holds weekly teleconferences, and primarily conducts its work on the public mailing list firstname.lastname@example.org (archive) for technical discussions. Group logistics are discussed in the public group list, email@example.com (archive) , or if needed the member-only mailing list firstname.lastname@example.org (archive).
The list of current members of the SVG WG is public.
As explained in the Process Document (section 3.3), this group seeks 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.
When the Chair conducts a formal vote to reach a decision on a substantive technical issue, eligible voters may vote on a proposal one of three ways: for a proposal, against a proposal, or abstain. For the proposal to pass there must be more votes for the proposal than against. In case of a tie, the Chair decides the outcome of the proposal. The Chair must only conduct a formal vote during a group meeting, and at least two-thirds of participants in Good Standing must be in attendance.
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.
This charter for the Scalable Vector Graphics (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.
Per process doc 6.2.3, the most important changes are summarised here.
$Date: 2012/03/21 13:32:37 $