Scalable Vector Graphics (SVG) is an XML markup language for describing two-dimensional vector graphics, both static and animated. It is an open standard created by the World Wide Web Consortium, which is also responsible for standards like HTML and XHTML.

Overview

SVG allows three types of graphic objects:

1. vector graphic shapes (e.g. paths consisting of straight lines and curves, and areas bounded by them)
2. raster graphics images / digital images
3. text

Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. Text can be in any XML namespace suitable to the application, which enhances searchability and accessibility of the SVG graphics. The feature set includes nested transformations, clipping paths, alpha masks , filter effects, template objects and extensibility.

SVG drawings can be dynamic and interactive. The Document Object Model (DOM) for SVG, which includes the full XML DOM, allows straightforward and efficient vector graphics animation via ECMAScript or SMIL. A rich set of event handlers such as onmouseover and onclick can be assigned to any SVG graphical object. Because of its compatibility and leveraging of other Web standards, features like scripting can be done on SVG elements and other XML elements from different namespaces simultaneously within the same web page.

If storage space is an issue, SVG images are sometimes saved with gzip compression, in which case they may be called "SVGZ files". Because XML contains a lot of redundant data, XML tends to compress very well and these files can be much smaller.

Mobile profiles

Because of industry demand with SVG 1.1 two mobile profiles were introduced: SVG Tiny (SVGT) and SVG Basic (SVGB). These are subsets of the full SVG standard, mainly intended for user agents with limited capabilities. In particular, SVG Tiny was defined for highly restricted mobile devices such as cellphones, and SVG Basic was defined for higher level mobile devices, such as PDAs.

Neither mobile profile includes support for the full DOM, while only SVG Basic has optional support for scripting, but because they are fully compatible subsets of the full standard most SVG graphics can still be rendered by devices which only support the mobile profiles.

The competing software Macromedia Flash Lite by Macromedia supports SVG Tiny since version 1.1.

Development history

SVG was developed in a long process after Macromedia and Microsoft introduced VML whereas Adobe Systems and Sun Microsystems submitted a competing format known as PGML .

SVG 1.0 became a W3C Recommendation on 2001-09-04 .

SVG 1.1 became a W3C Recommendation on 2003-01-14 .

SVG Tiny and SVG Basic (the Mobile SVG Profiles) became W3C Recommendations on 2003-01-14 .

SVG 1.2 is currently a W3C Working Draft.

Support for SVG in browsers and other applications

The use of SVG on the web is in its infancy. There is a great deal of inertia from the long-time use of completely raster formats, but also browser support is patchy, with users of most browsers having to install a plugin. Web sites which serve SVG images typically also provide the images in a raster format, either automatically by HTTP content negotiation or allowing the user to directly choose the file. Alternative images are usually automatically rasterised using a library such as ImageMagick, which provides a quick but incomplete implementation of SVG or Batik, which implements all of SVG, but is slower.

Some wikis have experimented with SVG support; it has been speculated that since SVG is a text-based format, a wiki might allow edits to SVG images in a fashion similar to editing an standard article. However, the benefits of editing images in this way are disputed. It is generally considered that even trivial editing is better achieved using a separate graphics package because it is difficult to visualise exactly how changes to the XML will appear on the final image. Current wikis mostly do not support either the display or editing of SVG images, partly because of the lack of full browser support, but also because rasterization using Batik is CPU-intensive and requires Sun's Java Runtime Environment, which is not free (as in freedom). In the spirit of being open, many wikis refuse to use non-free software, for example Jimbo Wales speaks about this here [1]. SVG support would be valuable to a wiki, especially for articles that require diagrams, so the situation may change in future, when ImageMagick is expanded to cover more of the SVG standard.

Plugin support

In most browsers, such as Internet Explorer, a plugin is needed to see SVG images in the browser window. Currently available SVG plugins include Adobe SVG Viewer and Corel SVG Viewer.

Native support

There are several advantages to native support. For example there is no need for a plug-in, SVG can be mixed with other formats in a single document, and scripting between different document formats is a lot more reliable.

The Mozilla SVG Project is working to bring native SVG support to Mozilla. A preview of the SVG support is expected to be included in the next official release of Mozilla Firefox. To turn the SVG support on, users will need to change a configuration preference.

The KDE project's Konqueror web browser also has a fairly complete SVG implementation called ksvg. Since they share the KHTML rendering engine, support will likely filter down to Apple's Safari browser in future. Elsewhere in KDE the format is finding greater use, and from version 3.4 onwards SVG wallpapers are supported.

SVG is natively supported in the Amaya web browser.

The Opera web browser (since 8.0 Beta 3) offers SVG support based on the SVG 1.1 Tiny standard.

Java programs can make use of the Batik SVG Toolkit to render, generate, and manipulate SVG graphics.

Tools

Most of the major drawing software packages such as Adobe Illustrator and Corel Draw support SVG export. OpenOffice.org Draw 1.1 and up can also export SVG files whilst SVGmaker creates SVG from standard Windows programs including the ubiquitous Office suite. Sodipodi and Inkscape are two other (open source, multi-platform) tools that use the SVG format. Sketsa is another native SVG Graphics Editor.

Similarly to XML, SVG has different kinds of standard parsers to read and write. An example of such technology is Batik from Apache. Batik supplies a set of standard modules like SVG Parser, SVG Generator and SVG DOM.

Projects that use SVG include Together, JFreeChart, and Compuware's OptimalJ.

Free tools

• Skencil (Website) SVG Editor, written almost entirely in Python
• Sodipodi (Website), Drawing application Unix and Windows, does not support animations
• Inkscape (Website), Sodipodi Fork with a greater focus on implementing the SVG standards and a different user interface.

See also

• Rich Internet Application
• Semantic Web
• 2D
• 3D computer graphics
• List of vector graphics markup languages
• Comparison of vector graphics markup languages

External links

• W3C SVG Pages
• Adobe SVG Plugin, Adobe SVG Demos
• Mozilla SVG and Mozilla SVG Demos
• SVGopen, annual international conference on Scalable Vector Graphics
• SVG maps and OpenSVGMapServer
• librsvg SVG renderer for GNOME, and Mozilla/Firebird plugin
• Sample SVG files created from popular programs
• ksvg SVG renderer for KDE/khtml
• SVG Perl module
• Article "SVG: A Sure Bet" by Paul Prescod
• Article "SVG Is The Future" by Kevin Hughes
• Vector-based Web Cartography: Enabler SVG
• Descriptions from Webreference
• discussion about free implementations
• VML Specification
• PGML Specification
• vmlsource.com
• Introduction to Vector Markup Language
• SVG Basics - beginner tutorials on SVG
• Sketsa - SVG Graphics Editor

SVG clipart

• Open Clip Art Library
• Sodipodi Clipart Page
• GNOME themes extras package
• Crystal Icons
• Gartoon Icons Theme
• BlueSphere Icon Theme

Example of embedded SVG image

Currently, SVG upload is disabled by mistake.

See also .