WD-SVGMobileReqs-20010803 24.3 KB

Raw Blame History Permalink

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <!-- SVG Mobile Requirements Document -->
  <!-- $Id: WD-SVGMobileReqs-20010803.html,v 1.6 2001/08/03 13:42:53 dean Exp $ -->
  <head>
	<title>SVG Mobile Requirements</title>

	<style type="text/css">

	  .designgoals {
		list-style-type: decimal;
	  }

	  .req-level1 {
		list-style-type: decimal;
		font-weight: bold;
	  }

	  .req-level2 {
		list-style-type: decimal;
		font-weight: normal;
	  }

	  .req-level1 li {
		margin-top: 1em;
	  }

	  .req-level2 li {
		margin-top: 0em;
	  }

	  .label {
		margin-top: 1em;
	  }

	  .comment {
		background: #ffffaa;
	  }

	  .svgversion {
		color: #336633;
		font-weight: bold;
	  }

	  .term {
		font-weight: bold;
		color: #aa3333;
	  }
	  </style>
	<link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />


  </head>


  <body>
	<div class="head">
	  <p>
	<a href="http://www.w3.org/" title="Go to W3C Home Page">
	  <img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/>
	</a>
	  </p>
	  <h1>SVG Mobile Requirements </h1>

	  <h2>W3C Working Draft 3 August 2001</h2>

	<dl>
	  <dt>This version:</dt>
	  <dd>
	<a href="http://www.w3.org/TR/2001/WD-SVGMobileReqs-20010803.html">http://www.w3.org/TR/2001/WD-SVGMobileReqs-20010803.html</a>
	  </dd>
	  <dt>Latest version:</dt>
	  <dd>
	<a href="http://www.w3.org/TR/SVGMobileReqs">http://www.w3.org/TR/SVGMobileReqs</a>
	  </dd>
	  <dt>
	Editors
	  </dt>
	  <dd>
	Rick Graham (BitFlash)
	<a href="mailto:rick@bitflash.com">
	  &lt;rick@bitflash.com&gt;
	</a>
	<br />
	Tolga Capin (Nokia)
	<a href="mailto:Tolga.Capin@nokia.com">
	  &lt;Tolga.Capin@nokia.com&gt;
	</a>
	  </dd>
	</dl>


<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Copyright"> Copyright</a> &copy;2001 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>&reg;</sup> (<a href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.inria.fr/"><abbr xml:lang="fr" lang="fr" title="Institut National de Recherche en Informatique et Automatique">INRIA</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>, <a href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software licensing</a> rules apply.</p>
</div>
	<hr />

	<h2><a name="abstract"></a>Abstract</h2>
	<p>
	  This document lists the design principles and requirements for
	  the creation of a mobile profile of the SVG specification to be
	  developed by the W3C SVG2 working group.
	</p>

    <h2><a name="status"></a>Status of this Document</h2>
    <p>
      This is a W3C Working Draft for review by W3C Members and other
      interested parties. It is a draft document and may be updated,
      replaced or made obsolete by other documents at any time. It is
      inappropriate to use W3C Working Drafts as reference material or
      to cite them as other than "work in progress". This is work in
      progress and does not imply endorsement by the <a
      href="http://www.w3.org/Consortium/Member/List">W3C
      membership</a>.
    </p>

    <p>
      This document was developed by the
      <a href="http://www.w3.org/Graphics/SVG/">Scalable Vector
	Graphics</a> (SVG) working group as part of the W3C
      <a href="http://www.w3.org/Graphics/">Graphics Activity</a>.
      The authors of this document are the SVG Working Group
      members.
    </p>

    <p>
      A list of current W3C Recommendations and other technical
      documents, including Working Drafts and Notes, can be found at
      <a href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.
    </p>

    <p>
      Feedback on this document should be sent to the email list <a
      href="mailto:www-svg2-comments@w3.org">www-svg2-comments@w3.org</a>. This
      is a public list that is archived. Public discussion of issues
      related to vector graphics on the Web and SVG in particular
      takes place on the <a href="mailto:www-svg@w3.org"> public
      mailing list of the SVG Working Group</a> (<a
      href="http://lists.w3.org/Archives/Public/www-svg/">list
      archives</a>). To subscribe send an email to
      <code>www-svg-request@w3.org</code> with the word
      <code>subscribe</code> in the subject line.
    </p>

    <p>
      <em>
	This section represents the status of this document at the time this
	version was published. It will become outdated if and when a new
	version is published. The latest status is maintained at the
	W3C.
      </em>
    </p>


	<h2><a name="contents"></a>Table of Contents</h2>

	<ul>
	  <li>
	1. <a href="#sec-introduction">Introduction</a>
	  </li>
	  <li>
	2. <a href="#sec-terminology">Terminology</a>
	  </li>
	  <li>
	3. <a href="#sec-usage">Usage Scenarios </a>
	  </li>
	  <li>
	4. <a href="#sec-design">Design Principles </a>
	  </li>
	  <li>
	5. <a href="#sec-requirements">Requirements</a>
	  </li>
	  <li>
	6. <a href="#sec-references">References</a>
	  </li>
	</ul>

	<div class="div1">
	  <h2><a name="sec-introduction"></a>1. Introduction</h2>
	  <p>
	The SVG 1.0 specification <a href="#ref-svg">[SVG 1.0]</a> is
	now a proposed recommendation.
	  </p>
	  <p>
	There is one area that has been identified as lacking in the
	SVG 1.0 Specification.  It has been established by industry demand,
	overwhelming support in the SVG working group and requests from the SVG
	developer community that some form of SVG suited to displaying vector
	graphics on small devices is required.  Moreover, the mission
	statement of SVG 1.0 specifically addresses small devices as a target
	area for vector graphics display.
	  </p>
	  <p>
	In order to meet these demands the SVG2 working group has
	committed to a concerted effort to create a profile
	specification that addresses this problem in a timely fashion.
	  </p>
	</div>

	<div class="div1">
	  <h2><a name="sec-terminology"></a>2. Terminology</h2>
	  <p>
	The following key words and phrases used throughout this
	document are defined here for clarity.  The terms Must,
	Should, and May are used to specify the extent to which an
	item is a requirement for the SVG working group in defining mobile
	profiles for SVG.  These recommendations should not be
	mistaken as a guide to implementors.
	  </p>
	  <ol>
	<li>
	  <b>'Must'</b>
	  means that the item is an absolute requirement.
	</li>
	<li>
	  <b>'Should'</b> means that there may exist valid reasons in
	  particular circumstances to ignore the item, but the full
	  implications must be understood and carefully weighed before
	  choosing a different course.
	</li>
	<li>
	  <b>'May' </b> means that
	  item will be considered, but further examination is
	needed to determine if the item should be treated as a requirement.
	</li>
	<li>
	  <b>'PDA' </b>
	  is a personal data assistant and refers to devices of that family
	  of mobile device.
	</li>
	<li>
	  <b>'Mobile device' </b>
	  refers to all manner of mobile devices that may be a candidate platform
	  for an SVG agent.  Mobile devices would include, but not be restricted to,
	  PDAs and mobile phones.
	</li>
	<li>
	  <b>'SVG' </b>
	  refers to SVG in general without reference to any version or profile.
	</li>
	<li>
	  <b>'SVG 1.0' </b>
	  refers to the original SVG specification.
	</li>
	<li>
	  <b>'SVG 1.1' </b>
	  refers to the version of SVG to be created that is a supreset of SVG 1.0 that has
	  been modularized to allow for easy generation of the SVGB and SVGT profiles.
	</li>
	<li>
	  <b>'SVG 2.0' </b>
	  refers to the final version of SVG to be produced as defined by the current charter.
	</li>
	<li>
	  <b>'SVGB' </b>
	  refers to SVG-Basic, a mid level SVG profile for somewhat restricted mobile devices.
	</li>
	<li>
	  <b>'SVGT' </b>
	  refers to SVG-Tiny, a low level SVG profile for very restricted mobile devices.
	</li>
	<li>
	  <b>'Mobile SVG' </b>
	  is used to refer to both SVGB and SVGT.
	</li>
	<li>
	  <b>'Rendering model' </b>
	  refers to the painters model of SVG defined in the SVG 1.0 specification.
	</li>
	  </ol>
	</div>


	<div class="div1">
	  <h2><a name="sec-usage"></a>3. Usage Scenarios</h2>
	  <p>
		The following usage scenarios illustrate some of the ways in which mobile
		SVG profiles might be used for various applications. They may be used as
		design cases during the development of mobile SVG profiles, and should
		be useful in helping non-members of the SVG Working Group to understand
		the intent and goals of this task.
	  </p>
		<p>
		Whatever the task delegated to SVG on small devices, the result will be
		reliable, scalable viewing of SVG documents and drawings anywhere.
		</p>
	  <p>
		<b>Location-Based Services. </b>
		Location-based services
		will be a default service in future systems. With location-based information
		and applications, mobile subscribers can access a wide range of services,
		such as traffic and weather reports, restaurant, theatre or movie ticket
		bookings. Interactive maps, representing points of interest, will be an
		important part of these services.
	  </p>
	  <p>
		<b>Mapping and Positioning. </b>
		GPS Transceivers make sense on mobile devices, SVG is a vector graphics
		format perfect for mapping.  SVG and Positioning will be a powerful combination
		on mobile devices.
	  </p>
	  <p>
		<b>Animated Picture Messaging.</b>
		Messaging is a
		popular service on cellular phones, which lets mobile phone users send
		and receive ring tones, picture messages, operator logos, business cards,
		calendar requests, Internet settings, etc., over wireless messaging
		transports.
	  </p>
	  <p>
		<b>Multimedia Messaging. </b>
		Multimedia Messaging
		is a continuation of SMS and Picture Messaging. MMS will let users exchange
		messages with rich content types including natural images, voice clips,
		video clips, and animated, interactive graphics.
	  </p>
	  <p>
		<b>Entertainment. </b>
		Interactive applications, such
		as games, cartoon animations, can be developed using mobile SVG profiles.
	  </p>
	<p>
		<b>Industrial Applications.</b>
		Field engineers locating and dealing with time critical construction and
		maintenance problems will be able to view maps and engineering plans in
		the field, on demand.
	</p>
	<p>
		<b>eCommerce.</b>
		Graphical views of stock data available on mobile devices will allow day
		traders to leave their desks, receive intelligent stock data and trade
		online, on the go.
	</p>
	<p>
		<b>User Interfaces.</b>
		SVG markup used to define look and feel for user interface controls will
		be used to allow vendors and users to add flexibility and accessibility
		to mobile device graphical user interfaces.
	</p>
	</div>


	<div class="div1">
	  <h2><a name="sec-design"></a>4. Design Principles</h2>

	  <ol>
		<li>It is recognized that some of the goals might conflict or be unachievable and that tradeoffs will have to be made.</li>
		<li> Two profiles must be designed to allow SVG to render on mobile devices with limited memory, CPU power, and bandwidth. </li>
		<li> Changes to SVG that do not contribute to (4.1) above will be resisted. </li>
		<li> Mobile SVG profiles should attempt to maximize compatibility with SVG 1.0 to display existing content.</li>
		<li> Extensions to SVG 1.0 will be allowed to support small device functionality.  The results of these extensions will be SVG 1.1</li>
		<li> There will be resistance to changes that make it difficult for vendors to alter their existing SVG applications. </li>
		<li>
	  There will be consideration for the items listed in the
          SVG 1.1/2.0 Requirements Document <a href="#ref-svgreqs">[SVG 1.1/2.0 Requirements]</a>.
		</li>
	<li> A true subset of the SVG 1.0 imaging model must be maintained.</li>
	<li> Mobile SVG should be designed to facilitate authoring tools.</li>
	<li>
		Mobile SVG should be designed so that SVG 1.1 can be transcoded into
		SVGB and SVGT preserving as much scalability as possible.
	</li>
		<li>
		  We don't believe that a single profile is sufficient to deal with the variety of
		mobile devices.  There will be two profiles, one low level (SVGT) for
		  restricted mobile devices, one for higher level mobile
		  devices (SVGB).
		</li>

	  </ol>
	</div>

	<div class="div1">
	  <h2><a name="sec-requirements"></a>5. Requirements</h2>
	  <ol class="req-level1">
	<li>General Requirements
	  <ol class="req-level2">
	    <li>
	      The profiles <span class="term">must</span> be international.
	    </li>
	    <li>
	      The rendering model of Mobile SVG <span class="term">must</span> be a true subset of the SVG 1.1 rendering model.
	    </li>
	    <li>
	      Mobile SVG <span class="term">must</span> consider constraints of handheld
	      devices, particularly low-power CPU, small displays,
	      limited interaction, low bandwidth and small memory.
	    </li>
	    <li>
	      Mobile SVG <span class="term">must</span> be a true subset of SVG 1.1, and use the
	      appropriate modules from SVG 1.1.
	    </li>
	    <li>
	      SVGT <span class="term">must</span> be a true subset of SVGB.
	    </li>
	    <li>
	      Conformance criteria for Mobile SVG <span
		class="term">must</span> be produced. The
	      criteria should be separated into sections
	      relevant to particular application types
	      (eg. Mobile SVG files/document fragments,
	      Mobile SVG generators, Mobile SVG Viewers,
	      etc)
	    </li>
	    <li>
	      Software or documents <span class="term">must</span> pass the relevant criteria to be able to
	      claim conformance to the particular application type.
	    </li>
	    <li>
	      A conformance test suite <span class="term">must</span> be developed for both profiles of Mobile SVG. The
	      test suite must be made publicly available.  Conformance test suites for other uses
	      of Mobile SVG (e.g. Accessibility guidelines) may be developed.
	    </li>
	    <li>
	      The SVG conformance test suite <span class="term">must</span> be a superset of the SVGB
	      conformance test suite.
	    </li>
	    <li>
	      The SVGB conformance test suite <span class="term">must</span> be a superset of the SVGT
	      conformance test suite.
	    </li>
	    <li>
	      Behaviour <span class="term">must</span> be specified to define how lower level
	      compliant agents will deal with content defined by
	      higher level profiles.
	      <ol>
		<li>
		  When an SVGT agent is presented with:
		  <ol>
		    <li>
		      SVGB
		    </li>
		    <li>
		      SVG 1.1
		    </li>
		  </ol>
		</li>
		<li>
		  When an SVGB agent is presented with SVG 1.1.
		</li>
	      </ol>
	    </li>
	  </ol>
	</li>
	<li>Supported Attribute Types
	  <ol class="req-level2">
		<li>
		  SVGB profile <span class="term">should</span> support 15.15 fixed point numbers.
		</li>
		<li>
		  SVGT profile <span class="term">may</span> support 15.15 fixed point numbers.
		</li>
	  </ol>
	</li>
	<li>Rendering Model
	  <ol class="req-level2">
		<li>
		  Mobile SVG has the same rendering model as SVG 1.1 but some language features may be restricted to
			address implementation constraints.
		</li>
	  </ol>
	</li>
	<li>Document Structure
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">should</span> support a large subset of use, image, and symbol.
		</li>
		<li>
		  SVGT <span class="term">may</span> support a subset of use, and symbol.
		</li>
		<li>
		  SVGT <span class="term">should</span> support raster formats and
			<span class="term">may</span> support the SVG format on the image element.
		</li>
		<li>
			Mobile SVG <span class="term">must</span> support a subset of the switch element.
		</li>
	  </ol>
	</li>
	<li>References and the 'defs' Element
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">must</span> support hyperlinking targets using the 'a' element.
		</li>
		<li>
		  All other referenced objects <span class="term">may</span> be internal.
		</li>
		<li>
		  There <span class="term">may</span> be restrictions on the use of the defs element.
		</li>
	  </ol>
	</li>
	<li>Styling
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">must</span> support a subset of SVG 1.1 presentation attributes.
		</li>
		<li>
		  Mobile SVG <span class="term">may</span> allow styling using CSS.
		</li>
	  </ol>
	</li>
	<li>Coordinate Systems, Transformations and Units
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">must</span> support viewports.
		</li>
		<li>
		  SVGT <span class="term">should</span> support viewports.
		</li>
		<li>
		  SVGB <span class="term">must</span> support nesting of transformations.
		</li>
		<li>
		  SVGT <span class="term">should</span> support nesting of transformations.
		</li>
		<li>
			SVGB <span class="term">should</span> support css unit types.
		</li>
		<li>
			SVGT lengths <span class="term">may</span> be restricted to values in user space.
			except for width and height attributes on the outermost svg element.
		</li>
	  </ol>
	</li>
	<li>Paths
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">must</span> support paths which can be filled and stroked.
		</li>
		<li>
		  SVGT <span class="term">must</span> support paths which can be filled.
		</li>
		<li>
		  SVGT <span class="term">should</span> support paths which can be stroked.
		</li>
		<li>
		  Mobile SVG <span class="term">must</span> support segment types of move, close, line, cubic and quadratic Bézier curves.
		</li>
		<li>
		  Mobile SVG <span class="term">may</span> support segment type elliptical curve.
		</li>
	  </ol>
	</li>
	<li>Basic Shapes
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">must</span> support basic shapes (rectangles, circles,
		  ellipses, lines, polylines, and polygons).
		</li>
	  </ol>
	</li>
	<li>Text
	  <ol class="req-level2">
		<li>
		  	Mobile SVG <span class="term">must</span> support international text.
			It is recognized that full support for international text may not be
			possible on small devices because of the complexity involved.
		</li>
		<li>
		  	SVGB <span class="term">should</span> support text on a path.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support text on a path.
		</li>
		<li>
		  	SVGB <span class="term">must</span> support a subset of tspan.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support a subset of tspan.
		</li>
	  </ol>
	</li>
	<li>Filling, Stroking, and Markers
	  <ol class="req-level2">
		<li>
		  	Mobile SVG <span class="term">must</span> support filling of paths and basic shapes with solid colors.
		</li>
		<li>
		  	SVGB <span class="term">must</span> support stroke and stroke-width on paths and basic shapes.
		</li>
		<li>
		  	SVGB <span class="term">should</span> support dashed stroke, line joins and end caps.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support stroke-width, dashed stroke, line joins and end caps.
		</li>
		<li>
		  	SVGB <span class="term">should</span> support stroked text where possible.
		</li>
		<li>
		  	SVGB <span class="term">should</span> support a subset of the marker feature
		  	set.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support a subset of the marker feature set.
		</li>
	  </ol>
	</li>
	<li>Color
	  <ol class="req-level2">
		<li>
		  	Mobile SVG <span class="term">must</span> support colors defined by 'color' property in
		  	sRGB color space.
		</li>
		<li>
		  	Mobile SVG <span class="term">should</span> support color keywords.
		</li>
	  </ol>
	</li>
	<li>Gradients and Patterns
	  <ol class="req-level2">
		<li>
		  	SVGB <span class="term">should</span> support gradients and patterns.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support a subset of gradients and patterns.
		</li>
	  </ol>
	</li>
	<li>Clipping, Masking and Compositing
	  <ol class="req-level2">
		<li>
		  	SVGB <span class="term">should</span> support clipping and masking, and compositing.
		</li>
		<li>
		  	SVGB <span class="term">may</span> not support additive clipping.
		</li>
		<li>
		  	SVGT <span class="term">may</span> support clipping, masking, and compositing.
		</li>
	  </ol>
	</li>
	<li>Filter Effects
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">may</span> support a subset of filter effects.
		</li>
	  </ol>
	</li>
	<li>Interactivity
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">must</span> support a large subset
		  of the SVG 1.1 interactivity feature set.
		</li>
		<li>
		  SVGT <span class="term">must</span> support a restricted subset
		  of the SVG 1.1 interactivity feature set.
		</li>
	  </ol>
	</li>
	<li>Linking
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">should</span> support a subset of the ability of SVG 1.0
		  to hyperlink into particular views of SVG content.
		</li>
		<li>
		  SVGT <span class="term">may</span> support a subset of the ability of SVG 1.0 to
		  hyperlink into particular views of SVG content.
		</li>
		<li>
		  SVGB <span class="term">must</span> support hyperlink activation from SVG content to
		  other Web resources.
		</li>
		<li>
		  SVGT <span class="term">should</span> support hyperlink activation from SVG content
		  to other Web resources.
		</li>
	  </ol>
	</li>
	<li>Scripting
	  <br />
	  <span class="req-level2">
		It is recognized that the the developer community considers scripting
		to be a powerful enabling device in SVG.  Scripting engines have
		large footprints however, and may be difficult to provide on small
		devices.  Scripting will be given careful consideration.
	  </span>
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">should</span> support the SVG 1.1 scripting feature set.
		</li>
		<li>
		  SVGT <span class="term">may</span> support the SVG 1.1 scripting feature set.
		</li>
	  </ol>
	</li>
	<li>Animation
	  <ol class="req-level2">
		<li>
		  SVGB <span class="term">must</span> support a large subset
		  of the animation elements and attributes from SVG 1.1.
		</li>
		<li>
		  SVGT <span class="term">must</span> support a restricted subset
		  of the animation elements and attributes from SVG 1.1.
		</li>
		<li>
		  The list of animatable elements, attributes and properties
		  in Mobile SVG <span class="term">should</span> be those elements,
		  attributes and properties available in the given profile,
		  animatable as defined in the SVG 1.1 specification.
		</li>
	  </ol>
	</li>
	<li>Fonts
	  <ol class="req-level2">
		<li>
		  	Mobile SVG <span class="term">should</span> support built-in system fonts.
		</li>
		<li>
		  SVGB <span class="term">must</span> support SVG fonts with glyph outlines expressed
		  using the "d" attribute on the &lt;glyph&gt; element
		</li>
		<li>
		  SVGT <span class="term">may</span> support SVG fonts with glyph outlines expressed
		  using the "d" attribute on the &lt;glyph&gt; element
		</li>
		<li>
		  Mobile SVG <span class="term">may</span> support SVG fonts with arbitrary SVG glyph content.
		</li>
	  </ol>
	</li>
	<li>Metadata and Extensibility
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">must</span> support embedded metadata.
		</li>
		<li>
		  Mobile SVG <span class="term">must</span> allow inclusion of elements and attributes
		  from foreign namespaces within the SVG content.
		</li>
	  </ol>
	</li>
	<li>SVG 1.1/2.0 Extensions Under Consideration
	  <ol class="req-level2">
		<li>
		  Mobile SVG <span class="term">may</span> include items proposed in the
		  SVG 1.1/2.0 Requirements Document
		  <a href="#ref-svgreqs">[SVG 1.1/2.0 Requirements]</a>.
		</li>
	  </ol>
	</li>
	  </ol>
	</div>
	<div class="div1">
	  <h2><a name="sec-references"></a>6. References</h2>
	  <dl class="references">
	<dt class="label"><a name="ref-svg"></a>SVG 1.0</dt>
	<dd>
	<em>Scalable Vector Graphics (SVG) 1.0 Specification</em>,
	Jon Ferraiolo, editor, W3C, 19 July 2001 (Proposed Recommendation). See
	<a href="http://www.w3.org/TR/2001/PR-SVG-20010719/">http://www.w3.org/TR/2001/PR-SVG-20010719/</a>
      </dd>

	<dt class="label"><a name="ref-svgreqs"></a>SVG 1.1/2.0 Requirements</dt>
	<dd>
	  <em>SVG 1.1/2.0 Requirements Document</em>,
	  Dean Jackson, editor, W3C, 3 August 2001. See
	  <a href="http://www.w3.org/TR/SVG2Reqs">http://www.w3.org/TR/SVG2Reqs</a>
	</dd>
	  </dl>
	</div>
  </body>
</html>