The working group will be chartered to both subset and extend the SVG 1.0 format, producing a modular XML tagset usable in mixed-XML namespace documents. SVG is a graphics format has been implemented in viewers and authoring tools and is now seeing adoption by the content authoring community as a replacement for many current uses of raster graphics. SVG 1.0 is suitable for desktop and palmtop systems. However, there is a need for a W3C-defined subset of SVG suitable for the particular requirements of mobile devices. There is also a need to improve printing, for example to allow multi-page print documents.
At the same time, several requirements were identified in the SVG 1.0 timeframe that could not be fully realised in the SVG 1.0 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.
This additional work will mean that the graphics in Web documents will be smaller, faster, 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 architectural constraints on the technology to be developed are:
- compatible with the principles of the Architecture document
- meet the needs of the user community
- be widely implementable in browsers and authoring tools
- make appropriate use of other W3C specifications
- be expressed in XML and usable as part of a larger XML document, using multiple namespaces
- Be based on the SVG 1.0 specification
- SVG Mobile Requirements document
- SVG 2.0 Requirements document
- SVG Mobile specification
- SVG 2.0 specification
- Proof of concept implementations
Tracking and Maintenance Items
- Publish comprehensive test suites for SVG Mobile and SVG 2.0 to aid developers in achieving SVG conformance
- Develop further test suite materials for SVG 1.0
- Monitoring of implementations for conformance, interoperability and quality. Publication of Implementation Reports.
- Collect errata and periodically publish new editions of the SVG specification incorporating errata
- Gather requirements for any subsequent version of SVG
Production of a stable document collectively addressing each of the Work Items, at Proposed Recommendation status.
Availability of multiple, independent, interoperable implementations of SVG, and authoring tools for SVG, including implementations on mobile devices and implementations.
This group will commence in June 2001 and will terminate in June 2003.
The group will create one or more Working Drafts, Test Suites, Implementation Reports, and track early implementations leading towards the release of further SVG specifications and the establishment of a deployed base of SVG conformant software.
The precise Working Drafts in production at a given time are listed on the WG page (W3C Member Only).
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 Member Only)
The SVG Working Group will develop a Royalty Free (RF) specification as defined by the Patent Policy Working Group.
Prior disclosure of Intellectual Property Rights pertaining to SVG is required at the time of the activity proposal and initial call for participation (W3C Member Only), and when an individual Member joins the Working Group. W3C Members agree to use good faith efforts to disclose all information known about patent claims that are likely to be essential to implement SVG specifications.
If during the course of its work the SVG WG incorporates a technology contribution as normative that is known to be contrary to the RF licensing requirement described here and in its Charter, then it must initiate an Ad Hoc Patent Advisory Group.
When specifications developed by the SVG Working Group go to each of these three stages: Last Call, Candidate Recommendation, and Proposed Recommendation, a call to identify patents likely to be essential to implement that specification shall be included as required by the Patent Policy WG . Any W3C member not willing to license particular essential technology on RF terms must opt-out specific patent claims they hold within 60 days after the issue of the specification for that stage. In consequence, the minimum period before entering the next stage (Last Call to Candidate recommendation, and Candidate recommendation to Proposed Recommendation) shall be 60 days.
A list of documents actively under consideration by the group (W3C Member Only), is maintained by the chair. To add a document to the list, or to revise a document in the list, the draft should be sent to the chair and/or the group mailing list. The chair will decide on new/revised drafts in collaboration with the group, provided the document falls within the scope of work items for the group.
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
- Hypertext Coordination Group (W3C Member Only)
- The SVG WG will coordinate its work with other Working Groups primarily through participation in the Hypertext Coordintion Group.
- XML Working Group (W3C Member Only)
- The SVG WG does not address changes to XML syntax. SVG will be written in XML 1.0, with the addition of XML namespaces.
- Document Object Model (DOM) (W3C Member Only)
- SVG content will be accessible from the XML Document Object Model.
- W3C Web Accessibility Initiative (W3C Member Only)
- The work of the SVG WG will be coordinated with the WAI project to ensure accessibility of SVG.
- XForms (W3C Member Only)
- Coordination with the Xforms Working Group will ensure that SVG will be usable as a rich presentation layer for XForms, allowing integration of form controls in SVG graphics.
- SYMM (W3C Member Only)
- Coordination with the SYMM WG or its successor will build on the joint work done to create SMIL Animation, and allow integration of SVG and SMIL 2.0
- XML Linking (W3C Member Only)
- The SVG format will continue to use the results of the XLink group for internal hyperlinking, linking into and out of the SVG graphic.
- CSS Working Group (W3C Member Only)
- 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.
- XSL Working Group (W3C Member Only)
- 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.
- Device Independence Activity
- The work of the SVG WG will be coordinated with this activity, in particular the Device Independence Working Group (W3C Member Only) and the Mobile Access Interest Group, to ensure that SVG can be used on a broader range of devices.
- Internationalization Working Group (W3C Member Only)
- The I18N WG will review the SVG specification to ensure it is adequately Internationalized.
One or more public Working Drafts, plus associated Test Suites and Implementation Reports, will be produced covering each of the Work Items, to the following schedule:
- first Working Group meeting: 11-13 June 2001, Ottawa, Canada
- SVG Mobile requirements document: July 2001
- SVG Mobile Last Call by October 2001
- SVG Mobile Candidate Recommendation by January 2002
- SVG Mobile Proposed Recommendation by April 2002
- SVG Mobile Recommendation by June 2002
- SVG Mobile Test Suite, first public release, by December 2001
- SVG Mobile Test Suite, final public release, by September 2002
- SVG 2.0 requirements document: August 2001
- SVG 2.0 Last Call by May 2002
- SVG 2.0 Candidate Recommendation by August 2002
- SVG 2.0 Proposed Recommendation by November 2002
- SVG 2.0 Recommendation by January 2003
- SVG 2.0 Test Suite, first public release, by July 2002
- SVG 2.0 Test Suite, final public release, by March 2003
A quarterly face to face meeting will be arranged. Meeting details are made available on the W3C Member Calendar and from the WG page (W3C Member Only)
Biweekly 90-minute phone conferences will be held. Minutes will be taken in rotation by WG members and mailed to the WG list within 24 hours.
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.
Participants (Working Group members, Invited experts, and W3C Team members) are required not to disclose information obtained during participation, until that information is publicly available.
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.