Summary

  • W3C's SVG 1.0 Recommendation of 4 September 2001 described two-dimensional graphics in XML: vector paths and shapes, images and text that could be grouped, styled and transformed.
  • Its coordinate and viewport rules let a drawing retain a geometric description while an author mapped a chosen area of it into a viewing window. The Web gained a drawing that could answer a zoom request with geometry rather than a larger copy of its original pixels.

Ask a tiny map to show one more street and it may reply with a row of enlarged squares. It can only repeat the samples it already has. A road described as a path has a different answer: here is the curve, here are its coordinates, and here is the window through which you want to see it. The SVG 1.0 Recommendation gave Web authors that kind of drawing language in 2001. Its subject was two-dimensional graphics in XML, with paths, basic shapes, images and text among the pieces an author could assemble.

The specification's introduction describes straight and curved vector paths alongside images and text. Those objects can be grouped, styled, transformed and composed. This matters for a map because roads, labels and boundaries are separate things with separate jobs. An author can draw a line through a set of places, put a name near it and move the group as a unit. A screenshot of that map presents the finished view; an SVG drawing carries the instructions and objects that make the view.

The clever part lives in the coordinate chapter. SVG distinguishes its canvas from the finite viewport where a reader actually sees content. It also distinguishes viewport coordinates from the drawing's user coordinates. The viewBox attribute selects a rectangle in that user space and maps it into the viewport. preserveAspectRatio helps determine how the rectangle fits. A larger frame, a smaller frame or a different chosen rectangle changes the view without forcing the author to redraw every road at a new pile of pixel addresses.

Once there are coordinates, the drawing can do more than politely sit still. Transformations change position, scale, rotation or skew. Groups can be transformed together; nested SVG elements can establish new viewports. A cartographer can place a city plan within a larger drawing and then choose which portion should fill a particular display area. The Web page receives a reusable set of geometric instructions instead of an image that begs everyone to stop zooming.

The format also included more than lines. The introduction lists text, embedded images, styling, clipping, masks, filters, animation and scripting among SVG's capabilities. Those features made the drawing a document of parts, with many ways to present or change them. For this 2001 story, the decisive shift is simpler: the author could name the geometry and the viewing relationship. A road remained a path even when the window changed.

The W3C announcement of 5 September 2001 described SVG 1.0 as an XML-based language for two-dimensional vector graphics. The Recommendation itself was dated the day before. That pair of records marks the moment when the Web gained a standard way to hand over a drawing's construction, not merely a picture of its current appearance. The next reader to lean into the map could ask to see the roads again. The roads had not dissolved into breakfast cereal.