The working group will be chartered to extend the SVG 1.1
format, producing a modular XML tagset usable in mixed-XML
namespace documents. SVG is a graphics format that has been
implemented in viewers and authoring tools and has been adopted by
the content authoring community as a replacement for many current
uses of raster graphics. SVG
1.1 is suitable for desktop and palmtop systems.
SVG Mobile Profiles: SVG
Basic and SVG Tiny are suitable for mobile and other resource
limited devices.

At the same time, several requirements were identified in the
SVG 1.1 timeframe that could not be fully realized in the SVG 1.1
specification. The principal request is greater integration with
other W3C specifications, such as XForms (to allow SVG form
controls); CSS and XSL (to allow wrapping styled text inside
graphics); and to ensure that SVG graphics can be placed inline in
multi-namespace XML documents. Also, SVG is often used as a
rendering library for XML documents. This has generated requests
for enhancement to the core SVG 1.1 language that would enable the
development of components (or extensions), allowing client-side
transformation of arbitrary XML content into SVG for display.
Furthermore there is a need to improve printing, for example to
allow multi-page print documents. Each enhancement to the core
language, along with each solution for integration with other
specifications, must be appropriate for all SVG usage scenarios.
In particular, SVG will consider the applicability to both
desktop and resource-limited devices, such as mobile devices
and printers.

The work on SVG will mean that the graphics in Web documents will
have a smaller file size, load faster, be more interactive, and be
displayable on a wider range of device resolutions from small mobile
devices through office computer monitors to high resolution
printers. This will be a significant advance in Web
functionality. Interoperability, both in multiple browsers across
multiple platforms and while being read and written by multiple
authoring tools, is a prime focus. See the
activity
statement for the overall goals and rationale of this activity
area.

The group will create one or more Working Drafts, Test Suites,
Implementation Reports addressing the technical, tracking and
maintenance items mentioned above, and track early implementations
leading towards the release of further SVG specifications and the
establishment of a deployed base of SVG conformant software.
The test suites will be distributed under the appropriate W3C Document
or Software licenses.

The precise Working Drafts in production at a given time are
listed on the WG
page.

The group will produce two Proposed Recommendations, drawn from
stable Working Drafts.

Minutes of teleconferences and face to face meetings are also
available from the
WG page

W3C promotes an open working environment. Whenever possible,
technical decisions should be made unencumbered by intellectual
property right (IPR) claims. This is a Royalty Free Working Group,
as described in W3C's Current Patent Practice.

Working Group participants disclose patent claims by sending
email to patent-issues@w3.org; please see Current Patent
Practice for more information about disclosures.

As documents stabilize, they will be released as
W3C Working Drafts. No
document may stay on the list of
documents
actively under consideration by the group for more than three
months without being released to the public as an intermediate
draft. Documents may be released sooner if consensus is
achieved. If the three month deadline is reached, the current draft
will be released (and not a draft from three months earlier). If,
before this time, anyone in the group feels the current draft will
not be not suitable for public release as an intermediate draft,
their options are:

move that the document be stricken from the list of work items.
(decision to be rendered by the chair in collaboration with the
group)

draft a revision of the document, before the deadline, which
the group agrees is suitable for interim public
release

The work of the SVG WG will be coordinated with this group to
ensure that SVG and mixed SVG/other namespace documents can be
styled, and that mixtures of SVG and XSL-FO namespace can be
generated by XSL-T stylesheets.

The Group works by consensus, including the use of straw polls.
In the event of failure to achieve consensus, the Group may resort
to a
vote
as described in the Process Document. Each Member company which has
at least one Group member in good standing may vote. There is one
vote per W3C Member company. Votes are held by email to allow all
participants a chance to vote; there is a two week voting period
followed by a period of two working days for the announcement of
the result. W3C staff and invited experts do not vote; however in
the event of a tie the chair has a casting vote. If the issue is
solved by consensus during the voting period, the vote is
cancelled.

Requirements for
meeting
attendance and timely response are described in the Process
document. Participation (meetings, reviewing and writing drafts) is
expected to consume time equal to 1 day per week for a period of
one year.

W3C Members may also offer to review one or more working drafts
from the group for clarity, consistency, technical merit, fitness
for purpose and conformance with other W3C specifications. They are
required to provide the review comments by the agreed-to date but
are not required to attend meetings.

As decided on a case by case basis, invited experts may attend a
single meeting or a series; they may in some cases be subscribed to
the Group mailing list. For the duration of their participation,
invited experts are encouraged to adopt the same requirements for
meeting attendance and timely response as are required of W3C
Members.

W3C Team will ensure that the mailing lists and Group page are
adequately maintained and that public Working Drafts are made
available on the Technical
Reports page. W3C Team will post minutes of teleconferences to
the Group mailing list and to the Group page.

A W3C Team member will provide liaison between any non-Team
document editors and the W3C Team; including posting revisions of
Working Drafts to the Group page.

W3C Team are expected to adopt the same requirements for meeting
attendance and timely response as are required of Working Group
members.