|
SVG is also the IATA code for Stavanger Airport, Sola in Norway. Scalable Vector Graphics (SVG) is an XML markup language for describing two-dimensional vector graphics, both static and animated, and either declarative or scripted. It is an open standard created by the World Wide Web Consortium.
Overview SVG allows three types of graphic objects: 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. An extreme example of this is a complete Tetris game implemented as an SVG object, found here. (The link requires an SVG enabled browser.) If storage space is an issue, SVG images can be saved with gzip compression, in which case they may be called "SVGZ files". Because XML contains verbose text, it tends to compress very well and these files can be much smaller. Often however the original vector-file (SVG) is already smaller than the rasterised version. Impact on the Web The widespread adoption of SVG clients, particularly those natively embedded in web browsers (as it is in Firefox and Opera), may bring a significant new look-and-feel to the World Wide Web. A current trend is to build dynamic web sites that behave somewhat like desktop applications, utilizing the Ajax technique. SVG enhances the capabilities of Ajax, by providing a rich, graphical set of page elements, well beyond those specified by HTML/CSS. The SVG Terminal module for Firefox is an early example of this. Development history SVG was developed by the W3C SVG Working Group starting in 1998, after Macromedia and Microsoft introduced Vector Markup Language (VML) whereas Adobe Systems and Sun Microsystems submitted a competing format known as PGML. The working group was chaired by Chris Lilley of the W3C. Mobile profiles Because of industry demand, two mobile profiles were introduced with SVG 1.1: 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. A listing of phones that support SVG can be found at the lsvg.org community web site. Support for SVG in browsers The use of SVG on the web is in its infancy. There is a great deal of inertia due to the long-time use of pure raster formats and other formats like Macromedia Flash or Java applets, but also browser support is still uneven, with native support in Opera and Firefox, but Safari and Internet Explorer requiring 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. Native support There are several advantages to native support, among which are no need for the installation of a plugin, the ability to freely mix SVG with other formats in a single document, and rendering scripting between different document formats considerably more reliable. At this time all major browsers have committed to some level of SVG support except for Internet Explorer. See Comparison of layout engines for further details. Plugin support In browsers such as Internet Explorer and Safari, a plugin is needed to view SVG content. The most widely available SVG plugin on the desktop is from Adobe Systems and supports most of SVG 1.0/1.1. (Adobe's SVG download page now says "Please note that Adobe has announced that it will discontinue support for Adobe SVG Viewer on January 1, 2008.") The current version of Safari ships with the plugin, while Internet Explorer users must separately download it. A legacy plugin was once offered from Corel. Support in applications 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 except for declarative animation but requires the Java Runtime Environment. Some viewers are listed in external links. Mobile support On mobile, the most popular implementations for mobile phones are by Ikivo and Bitflash, while for PDAs, Bitflash and Intesis have implementations. Flash Lite by Macromedia optionally supports SVG Tiny since version 1.1. At the SVG Open 2005 conference, Sun demonstrated a mobile implementation of SVG Tiny 1.1 for the CDLC platform. Mobile svg players from Ikivo and BitFlash come pre-installed i.e. manufacturer burn the SVG player code in their mobiles before shipping to the customers. Level of SVG Tiny support varies from mobile to mobile depending on the manufacturer and version of the svg player installed. Many of the new mobiles support additional features beyond SVG Tiny 1.1, like gradient and opacity. SVG and wikis 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 a 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. Some wikis do not support natively displaying or editing SVG images in a web browser. However, some wikis can render SVG images as raster images, to be more compatible with browsers that do not have native SVG support. SVG support would be valuable to a wiki, especially for articles that require diagrams, so the situation may change in the future, when ImageMagick is expanded to cover more of the SVG standard, and work on allowing Batik to run on a completely free Java implementation is complete *. The MediaWiki software used to run Wikipedia currently supports the SVG format. However, when rasterizing SVG images, it does not render some fonts like Verdana, and instead uses Arial. See also Demos Libraries Tutorials Articles Viewers, Editors and Converters see SVG Tools or the SVG Implementations Directory svgi.org | |||||||||||||||||||||
|
| ||||||||||||||||||||||
 |
|
| |