1
<?xml version="1.0" encoding="UTF-8"?>
2
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
3
<html xmlns="http://www.w3.org/1999/xhtml">
5
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
6
<title>Introduction – SVG Tiny 1.2</title>
7
<link rel="stylesheet" href="style/svg-style.css" type="text/css"/>
8
<link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-REC" type="text/css"/>
9
<link rel="contents" href="expanded-toc.html"/>
10
<link rel="next" href="concepts.html"/>
15
SVG Tiny 1.2 – 20081222
17
<li><a href="index.html">Top</a></li>
18
<li><a href="expanded-toc.html">Contents</a></li>
19
<li><a href="concepts.html">Next</a></li>
20
<li><a href="elementTable.html">Elements</a></li>
21
<li><a href="attributeTable.html">Attributes</a></li>
25
<h1>1 Introduction</h1>
27
<h2 id="toc">Contents</h2>
29
<li>1.1 <a href="intro.html#AboutSVG">About SVG</a></li>
30
<li>1.2 <a href="intro.html#SVGTiny12">SVG Tiny 1.2</a>
32
<li>1.2.1 <a href="intro.html#Profiling">Profiling the SVG specification</a></li>
34
<li>1.3 <a href="intro.html#defining">Defining an SVG Tiny 1.2 document</a></li>
35
<li>1.4 <a href="intro.html#mimetype">SVG MIME type, file name extension and Macintosh file type</a></li>
36
<li>1.5 <a href="intro.html#compatibility">Compatibility with other standards efforts</a></li>
37
<li>1.6 <a href="intro.html#Definitions">Definitions</a></li>
38
<li>1.7 <a href="intro.html#howtoreference">How to reference this specification</a></li>
39
<li>1.8 <a href="intro.html#howtouse">How to use this specification</a></li>
41
<h2 id="AboutSVG">1.1 About SVG</h2>
44
SVG is a language for describing two-dimensional graphics in
45
XML [<a href="refs.html#ref-XML10">XML10</a>, <a href="refs.html#ref-XML11">XML11</a>].
46
SVG allows for three types of graphic objects: vector graphic
47
shapes (e.g., paths consisting of straight lines and curves),
48
multimedia (such as raster images, video, and audio), and text.
49
Graphical objects can be grouped, styled,
50
transformed and composited into previously rendered objects.
53
SVG documents can be <a href="interact.html">interactive</a>
54
and <a href="animate.html">dynamic</a>. <a href="animate.html">Animations</a>
55
can be defined and triggered either declaratively (i.e., by embedding SVG
56
<a href="intro.html#TermAnimationElement"><span class="svg-term">animation elements</span></a> in SVG content) or via scripting.
59
Sophisticated applications of SVG are possible by use of a
60
supplemental scripting language which accesses the
61
<a href="svgudom.html">SVG Micro Document Object Model (uDOM)</a>, which
62
provides complete access to all elements, attributes and
63
properties. A rich set of <a href="interact.html#SVGEvents">event handlers</a>
64
can be assigned to any SVG graphical object. Because of its
65
<a href="intro.html#compatibility">compatibility and leveraging
66
of other Web standards</a>, features like <a href="script.html">scripting</a>
67
can be done on XHTML and SVG elements simultaneously within the same Web page.
70
SVG is a language for rich graphical content. For
71
accessibility reasons, if there is an original source document
72
containing higher-level structure and semantics, it is
73
recommended that the higher-level information be made available
74
somehow, either by making the original source document
75
available, or making an alternative version available in a
76
format which conveys the higher-level information,
77
or by using SVG's facilities to include the higher-level
78
information within the SVG content. For suggested techniques in
79
achieving greater accessibility, see <a href="access.html">Accessibility</a>.
82
It is believed that this specification is in accordance with the Web Architecture
83
principles as described in
84
<a href="../../2004/REC-webarch-20041215/index.html"><cite>Architecture of
85
the World Wide Web</cite></a> [<a href="refs.html#ref-AWWW">AWWW</a>].
88
<h2 id="SVGTiny12">1.2 SVG Tiny 1.2</h2>
91
Industry demand, overwhelming support in the SVG working group and
92
requests from the SVG developer community established the need for
93
some form of SVG suited to displaying vector graphics on small
94
devices. Moreover, the mission statement of SVG 1.0 specifically
95
addressed small devices as a target area for vector graphics display.
96
In order to meet these demands the SVG Working Group created a profile
97
specification that was suitable for use on mobile devices as well as
99
<a href="http://www.w3.org/TR/SVGMobile/"><cite>Mobile SVG Profiles</cite></a>
100
specification [<a href="refs.html#ref-SVGM11">SVGM11</a>]
101
(also known as SVG Mobile 1.1)
102
addressed that requirement and defined two profiles to deal with
103
the variety of mobile devices having different characteristics in
104
terms of CPU speed, memory size, and color support. The SVG Mobile
105
1.1 specification defined SVG Tiny (SVGT) 1.1, suitable for highly
106
restricted mobile devices; it also defined a second profile, SVG
107
Basic (SVGB) 1.1, targeted for higher level mobile devices. The major
108
difference between SVG Tiny 1.1 and SVG Basic 1.1 was the absence
109
of scripting and styling in SVG 1.1 Tiny, and thus any requirement
110
to maintain a Document Object Model (DOM). This saved a substantial
111
amount of memory in most implementations.
114
Experience with SVG Tiny 1.1, which was widely adopted in the industry
115
and shipped as standard on a variety of cellphones, indicated that the
116
profile was a little too restrictive in some areas. Features from SVG
117
1.1 such as gradients and opacity were seen to have substantial value
118
for creating attractive content, and were shown to be implementable on
119
cellphones. There was also considerable interest in adding audio and
120
video capabilities, building on the SMIL support in SVG Tiny 1.1.
123
Advances such as DOM Level 3, which introduces namespace support and
124
value normalization, prompted a second look at the use of programming
125
languages and scripting with SVG Tiny. In conjunction with the Java
126
<a href="http://www.jcp.org/en/jsr/detail?id=226">JSR 226 group</a>
127
[<a href="refs.html#ref-jsr226">JSR226</a>], a lightweight interface
128
called the Micro DOM, or uDOM, was developed. This could be, but
129
need not be, implemented on top of DOM Level 3. With this advance,
130
lightweight programmatic control of SVG (for example, for games or
131
user interfaces) and use with scripting languages, became feasible on
132
the whole range of platforms from cellphones through to desktops. In
133
consequence, there is only a single Mobile profile for SVG 1.2: SVG
137
This specification defines the features and syntax for
138
<a href="http://www.w3.org/Graphics/SVG/">Scalable Vector Graphics (SVG)</a>
139
Tiny 1.2, the core specification and baseline profile of SVG 1.2.
140
Other SVG specifications will extend this baseline functionality
141
to create supersets (for example, SVG 1.2 Full). The SVG Tiny 1.2
142
specification adds to SVG Tiny 1.1 features requested by SVG authors,
143
implementors and users; SVG Tiny 1.2 is a superset of SVG Tiny 1.1.
146
<h3 id="Profiling">1.2.1 Profiling the SVG specification</h3>
148
The Tiny profile of SVG 1.2 consists of all of the features defined
149
within this specification. As a baseline specification, it is possible
150
for: <em>superset profiles</em> (e.g., SVG Full 1.2) which include
151
all of the Tiny profile but add other features to the baseline;
152
<em>subset profiles</em>; and <em>special-purpose profiles</em> which
153
incorporate some modules from this specification in combination with
154
other features as needed to meet particular industry requirements.
157
When applied to conformance, the term "SVG Tiny 1.2" refers to
158
the Tiny profile of SVG 1.2 defined by this specification. If an
159
implementation does not implement the Tiny profile completely, the
160
UA's conformance claims must state either the profile to which it
161
conforms and/or the specific set of features it implements.
164
<h2 id="defining">1.3 Defining an SVG Tiny 1.2 document</h2>
167
SVG Tiny 1.2 is a backwards compatible upgrade to
168
<a href="http://www.w3.org/TR/SVGMobile/">SVG Tiny 1.1</a>
169
[<a href="refs.html#ref-SVGM11">SVGM11</a>]. Backwards compatible means that
170
conformant SVG Tiny 1.1 content will render the same in conformant
171
<a href="intro.html#TermSVGUserAgent"><span class="svg-term">SVG Tiny 1.2 user agents</span></a> as it did in conformant SVG Tiny 1.1 user agents.
172
A few key differences from SVG Tiny 1.1 should be noted:
178
<a href="struct.html#SVGElementVersionAttribute"><span class="attr-name">'version'</span></a>
180
<a href="intro.html#TermRootmostSVGElement"><span class="svg-term">rootmost 'svg' element</span></a>
181
should be <span class="attr-value">'1.2'</span>. See the
182
<a href="implnote.html#VersionControl">description of version control</a>
183
in the Implementation Requirements appendix for details.
188
There is no DTD for SVG 1.2, and therefore no need to specify the DOCTYPE
189
for an SVG 1.2 document (unless it is desired to use the
190
<a href="http://www.w3.org/TR/2004/REC-xml11-20040204/#NT-intSubset">internal DTD subset</a>
191
([<a href="refs.html#ref-XML10">XML10</a>], section 2.8,
192
and [<a href="refs.html#ref-XML11">XML11</a>], section 2.8),
193
for purposes of entity definitions for example). Instead, identification
194
is by the SVG namespace, plus the
195
<a href="struct.html#SVGElementVersionAttribute"><span class="attr-name">'version'</span></a>
196
and <a href="struct.html#SVGElementBaseProfileAttribute"><span class="attr-name">'baseProfile'</span></a>
197
attributes. In SVG Tiny 1.2, validation can be performed using the
198
<a href="schema.html">RelaxNG schema</a>.
203
The namespace for SVG Tiny 1.2 is the same as that of SVG 1.0 and 1.1,
204
<code>http://www.w3.org/2000/svg</code> and is
205
<a href="http://www.w3.org/2001/tag/doc/namespaceState.html#namespacedef"><em>mutable</em></a>
206
[<a href="refs.html#ref-NSState">NSState</a>]; names may be added over time
207
by the W3C SVG Working Group by publication in W3C Technical Reports.
210
Here is an example of an SVG Tiny 1.2 document:
213
<div class="example"><div class="exampleheader"><strong>Example:</strong> <a href="examples/01_01.svg">01_01.svg</a></div><div class="examplesource"><pre><?xml version="1.0"?>
214
<svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny"
215
viewBox="0 0 30 30">
216
<desc>Example SVG file</desc>
217
<rect x="10" y="10" width="10" height="10" fill="red"/>
222
Here is an example of defining an entity in the internal DTD subset.
223
Note that in XML, there is no requirement to fetch the external DTD
224
subset and so relying on an external subset reduces interoperability.
225
Also note that the SVG Working Group does not provide a normative DTD
226
for SVG Tiny 1.2 but instead provides a normative RelaxNG schema.
229
<div class="example"><div class="exampleheader"><strong>Example:</strong> <a href="examples/entity.svg">entity.svg</a></div><div class="examplesource"><pre><?xml version="1.0" encoding="UTF-8"?>
232
<rect x='.5' y='.5' width='29' height='39' fill='black' stroke='red'/>
233
<g transform='translate(0, 5)'>
234
<circle cx='15' cy='15' r='10' fill='yellow'/>
235
<circle cx='12' cy='12' r='1.5' fill='black'/>
236
<circle cx='17' cy='12' r='1.5' fill='black'/>
237
<path d='M 10 19 L 15 23 20 19' stroke='black' stroke-width='2'/>
241
<svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny">
242
<title>Smiley face</title>
244
This example shows the use of an entity defined in the
245
internal DTD subset. Note that there is no external DTD subset
246
for SVG Tiny 1.2, and thus no formal public identifier.
253
<h2 id="mimetype">1.4 SVG MIME type, file name extension and Macintosh file type</h2>
256
The MIME type for SVG is <code>"image/svg+xml"</code> (see
257
<a href="mimereg.html">Media type registration for image/svg+xml</a>).
260
It is recommended that SVG files have the extension <code>".svg"</code> (all
261
lowercase) on all platforms. It is recommended that
262
<a href="http://www.ietf.org/rfc/rfc1952.txt">gzip</a>-compressed
263
SVG files have the extension <code>".svgz"</code> (all lowercase) on all
264
platforms [<a href="refs.html#ref-RFC1952">RFC1952</a>].
267
It is recommended that SVG files stored on Macintosh HFS
268
file systems be given a file type of <code>"svg "</code>
269
(all lowercase, with a space character as the fourth letter).
270
It is recommended that gzip-compressed
271
SVG files stored on Macintosh HFS file systems be given a file
272
type of <code>"svgz"</code> (all lowercase).
275
(See <a href="conform.html">Conformance Criteria</a> for more information
276
about gzip-compressed SVG files transmitted over HTTP.)
279
<h2 id="compatibility">1.5 Compatibility with other standards efforts</h2>
282
SVG Tiny 1.2 leverages and integrates with other W3C specifications
283
and standards efforts. By leveraging and conforming to other
284
standards, SVG becomes more powerful and makes it easier for users to
285
learn how to incorporate SVG into their Web sites.
288
The following describes some of the ways in which SVG maintains
289
compatibility with, leverages and integrates with other W3C
295
SVG Tiny 1.2 is an application of XML and is compatible with both the
296
<a href="../../2006/REC-xml11-20060816/index.html"><cite>Extensible Markup Language (XML) 1.1</cite></a>
297
[<a href="refs.html#ref-XML11">XML11</a>] and
298
<a href="http://www.w3.org/TR/2006/REC-xml-20060816/"><cite>Extensible Markup Language (XML) 1.0 (Third Edition)</cite></a>
299
[<a href="refs.html#ref-XML10">XML10</a>] Recommendations.
304
SVG Tiny 1.2 is compatible with both the
305
<a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/"><cite>Namespaces in XML 1.0</cite></a>
306
[<a href="refs.html#ref-XML-NS10">XML-NS10</a>] and the
307
<a href="../../2006/REC-xml-names11-20060816/index.html"><cite>Namespaces in XML 1.1</cite></a>
308
[<a href="refs.html#ref-XML-NS">XML-NS</a>] Recommendations.
313
SVG Tiny 1.2 utilizes
314
<a href="../../2001/REC-xlink-20010627/index.html"><cite>XML Linking Language (XLink) </cite></a>
315
[<a href="refs.html#ref-XLINK10">XLINK10</a>] for IRI
316
referencing and requires support for base IRI specifications
317
defined in <a href="http://www.w3.org/TR/2001/REC-xmlbase-20010627/"><cite>XML Base</cite></a>
318
[<a href="refs.html#ref-XML-BASE">XML-BASE</a>].
323
SVG Tiny 1.2 uses the <a href="struct.html#xmlIDAttribute"><span class="attr-name">'xml:id'</span></a>
324
attribute as defined in
325
<a href="../../2005/REC-xml-id-20050909/index.html"><cite>xml:id Version 1.0</cite></a>
326
[<a href="refs.html#ref-xmlid">XMLID</a>].
331
SVG Tiny 1.2 content can be generated using
332
<a href="../../1999/REC-xslt-19991116.html"><cite>XSL Transformations (XSLT) Version 1.0</cite></a>
333
[<a href="refs.html#ref-XSLT">XSLT</a>] or
334
<a href="../../2007/REC-xslt20-20070123/index.html"><cite>Version 2.0</cite></a>
335
[<a href="refs.html#ref-XSLT2">XSLT2</a>]. (See
336
<a href="styling.html#StylingWithXSL">Styling with XSL</a>.)
341
SVG Tiny 1.2 supports formatting properties drawn from CSS and XSL. (See
342
<a href="styling.html#SVGStylingProperties">SVG's styling properties</a>).
347
SVG Tiny 1.2 includes a compatible subset of the Document Object Model (DOM) and
348
supports many of the facilities described in
349
<a href="../../2004/REC-DOM-Level-3-Core-20040407/index.html"><cite>Document Object Model (DOM) Level 3 Core</cite></a>
350
[<a href="refs.html#ref-DOM3">DOM3</a>], including namespace support and event handling.
355
SVG Tiny 1.2 incorporates some features from the
356
<a href="../../2005/REC-SMIL2-20051213/index.html"><cite>Synchronized Multimedia
357
Integration Language (SMIL) 2.1 Specification</cite></a>
358
[<a href="refs.html#ref-SMIL21">SMIL21</a>], including the
359
<a href="struct.html#PrefetchElement"><span class="element-name">'prefetch'</span></a>
360
and <a href="struct.html#SwitchElement"><span class="element-name">'switch'</span></a>
361
elements, the <a href="struct.html#SystemLanguageAttribute"><span class="attr-name">'systemLanguage'</span></a>
362
attribute, animation features (see <a href="animate.html">Animation</a>)
363
and the ability to reference audio and video media (see
364
<a href="multimedia.html">Multimedia</a>). SVG's animation features
365
incorporate and extend the general-purpose XML animation capabilities
366
described in SMIL 2.1. In addition, SVG Tiny 1.2 has been designed to
367
allow SMIL 2.1 to use animated or static SVG content as media components.
372
SVG is compatible with W3C work on internationalization. References (W3C
373
and otherwise) include:
374
<a href="http://www.unicode.org/unicode/standard/versions/"><cite>The Unicode Standard</cite></a>
375
[<a href="refs.html#ref-UNICODE">UNICODE</a>]
377
<a href="../../2005/REC-charmod-20050215/index.html"><cite>Character Model for the World Wide Web 1.0</cite></a>
378
[<a href="refs.html#ref-CHARMOD">CHARMOD</a>].
379
(See <a href="i18n.html">Internationalization Support</a>.)
384
SVG is compatible with W3C work on
385
<a href="http://www.w3.org/WAI/">Web Accessibility</a>
386
[<a href="refs.html#ref-WAI">WAI</a>]. (See
387
<a href="access.html">Accessibility Support</a>).
392
In environments which support the
393
<a href="../../2004/REC-DOM-Level-3-Core-20040407/index.html"><cite>Document Object Model (DOM) Core</cite></a>
394
[<a href="refs.html#ref-DOM3">DOM3</a>] for other XML grammars (e.g.,
395
<a href="../../2002/REC-xhtml1-20020801/index.html"><cite>XHTML 1.0</cite></a>
396
[<a href="refs.html#ref-XHTML">XHTML</a>]) and which also
397
support SVG and the SVG DOM, a single scripting approach can be
398
used simultaneously for both XML documents and SVG graphics, in
399
which case interactive and dynamic effects will be possible on
400
multiple XML namespaces using the same set of scripts.
403
<h2 id="Definitions">1.6 Definitions</h2>
406
When used in this specification, terms have the meanings assigned in
410
<dl class="definitions">
411
<dt id="TermAfterEdge">after-edge</dt>
413
Defined in the <a href="../../2006/REC-xsl11-20061205/index.html#area_model">XSL Area
414
Model</a> ([<a href="refs.html#ref-XSL">XSL</a>], section 4.2.3).
417
<dt id="TermAnimationElement">animation element</dt>
419
Using the various animation elements, you can define motion paths,
420
fade-in or fade-out effects, and allow objects to grow, shrink, spin or
421
change color. The following five elements are animation elements:
422
<a href="animate.html#AnimateElement"><span class="element-name">'animate'</span></a>,
423
<a href="animate.html#AnimateColorElement"><span class="element-name">'animateColor'</span></a>,
424
<a href="animate.html#AnimateMotionElement"><span class="element-name">'animateMotion'</span></a>,
425
<a href="animate.html#AnimateTransformElement"><span class="element-name">'animateTransform'</span></a>
427
<a href="animate.html#SetElement"><span class="element-name">'set'</span></a>.
428
Animation elements are further described in
429
<a href="animate.html#Animation.class">Animation elements</a>.
432
<dt id="TermBasicShape">basic shape</dt>
434
Standard shapes which are predefined in SVG as a convenience for common
435
graphical operations. Specifically, any instance of the following
437
<a href="shapes.html#CircleElement"><span class="code-fragment">'circle'</span></a>,
438
<a href="shapes.html#EllipseElement"><span class="code-fragment">'ellipse'</span></a>,
439
<a href="shapes.html#LineElement"><span class="code-fragment">'line'</span></a>,
440
<a href="shapes.html#PolygonElement"><span class="code-fragment">'polygon'</span></a>,
441
<a href="shapes.html#PolylineElement"><span class="code-fragment">'polyline'</span></a> and
442
<a href="shapes.html#RectElement"><span class="code-fragment">'rect'</span></a>.
445
<dt id="TermBeforeEdge">before-edge</dt>
447
Defined in the <a href="../../2006/REC-xsl11-20061205/index.html#area_model">XSL Area
448
Model</a> ([<a href="refs.html#ref-XSL">XSL</a>], section 4.2.3).
451
<dt id="TermCanvas">canvas</dt>
453
A surface onto which <a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics elements</span></a> are drawn, which can be real
454
physical media such as a display or paper or an abstract surface such
455
as a allocated region of computer memory. See the
456
<a href="coords.html#Introduction">description of the canvas</a> in
457
the <a href="coords.html">Coordinate Systems, Transformations and
461
<dt id="TermBoundingBox">bounding box</dt>
463
A bounding box is the tightest fitting rectangle aligned with the axes of
465
<a href="intro.html#TermUserCoordinateSystem"><span class="svg-term">user coordinate system</span></a>
466
that entirely encloses it and its descendants. For details, see the
467
<a href="coords.html#BoundingBox">description of the bounding box</a> in
468
the <a href="coords.html">Coordinate Systems, Transformations and Units</a>
472
<dt id="TermConditionalProcessingAttribute">conditional processing attribute</dt>
475
A conditional processing attribute is one of the five attributes that may
476
appear on most <a href="intro.html#TermSVGElement"><span class="svg-term">SVG elements</span></a> to control whether or not that element will
477
be processed. Those attributes are
478
<a href="struct.html#RequiredExtensionsAttribute"><span class="attr-name">'requiredExtensions'</span></a>,
479
<a href="struct.html#RequiredFeaturesAttribute"><span class="attr-name">'requiredFeatures'</span></a>,
480
<a href="struct.html#RequiredFontsAttribute"><span class="attr-name">'requiredFonts'</span></a>,
481
<a href="struct.html#RequiredFormatsAttribute"><span class="attr-name">'requiredFormats'</span></a> and
482
<a href="struct.html#SystemLanguageAttribute"><span class="attr-name">'systemLanguage'</span></a>.
486
<dt id="TermContainerElement">container element</dt>
488
An element which can have <a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics elements</span></a> and other
489
container elements as child elements. Specifically,
490
the following elements are container elements:
491
<a href="linking.html#AElement"><span class="code-fragment">'a'</span></a>,
492
<a href="struct.html#DefsElement"><span class="code-fragment">'defs'</span></a>,
493
<a href="struct.html#GElement"><span class="code-fragment">'g'</span></a>,
494
<a href="struct.html#SVGElement"><span class="code-fragment">'svg'</span></a>
496
<a href="struct.html#SwitchElement"><span class="code-fragment">'switch'</span></a>.
499
<dt id="TermCurrentSVGDocumentFragment">current SVG document fragment</dt>
502
The current SVG document fragment of an element is the XML document
506
<li>The sub-tree is a valid <a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>.</li>
507
<li>The sub-tree contains the element in question.</li>
508
<li>All ancestors of the element in question in the sub-tree are
509
elements in the SVG language and namespace.</li>
511
<p>A given element may have no current SVG document fragment.</p>
514
<dt id="TermCurrentTransformationMatrix">current transformation matrix
517
Transformation matrices define the mathematical mapping
518
from one coordinate system into another using a 3x3 matrix
520
<span class="code-fragment">[x' y' 1] = [x y 1] * matrix</span>.
521
The current transformation matrix defines the mapping from the
522
<a href="intro.html#TermUserCoordinateSystem"><span class="svg-term">user coordinate system</span></a> into the
523
<a href="intro.html#TermViewportCoordinateSystem"><span class="svg-term">viewport
524
coordinate system</span></a>. See
525
<a href="coords.html#EstablishingANewUserSpace">Coordinate
526
system transformations</a>.
529
<dt id="TermDecoratedBoundingBox">decorated bounding box</dt>
532
The decorated bounding box follows the definition for
533
<a href="intro.html#TermBoundingBox"><span class="svg-term">bounding
534
box</span></a>, with the exception that it takes into account not
535
only the geometry, but also all geometry-based drawing operations that
536
are marked in their definitions as contributing to this calculation.
540
<dt id="TermDescriptiveElement">descriptive element</dt>
542
An element, not itself in the <a href="intro.html#TermRenderingTree"><span class="svg-term">rendering tree</span></a>, which provides supplementary information about the <a href="intro.html#TermContainerElement"><span class="svg-term">container element</span></a> or <a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics element</span></a> to which it applies (i.e., the described element or elements). Specifically, the following elements are descriptive elements:
543
<a href="struct.html#DescElement"><span class="element-name">'desc'</span></a>,
544
<a href="metadata.html#MetadataElement"><span class="element-name">'metadata'</span></a>, and
545
<a href="struct.html#TitleElement"><span class="element-name">'title'</span></a>.
548
<dt id="TermDocumentBegin">document begin</dt>
551
The document begin for a given <a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a> is the time at
552
which the document's timeline is considered to begin. It depends on the
554
<a href="struct.html#SVGElementTimelineBegin"><span class="attr-name">'timelineBegin'</span></a>
559
If <a href="struct.html#SVGElementTimelineBegin"><span class="attr-name">'timelineBegin'</span></a>
560
is <span class="attr-value">'onLoad'</span>, then the document begin
561
is the exact time at which the
562
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
563
element's <a href="interact.html#EventsLoad"><code>load</code></a>
568
<a href="struct.html#SVGElementTimelineBegin"><span class="attr-name">'timelineBegin'</span></a>
569
is <span class="attr-value">'onStart'</span>, then the document begin
570
is the exact time at which the
571
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
573
<a href="http://www.w3.org/TR/2006/REC-xml-20060816/#sec-starttags">start-tag</a>
574
([<a href="refs.html#ref-XML10">XML10</a>,
575
<a href="refs.html#ref-XML11">XML11</a>], section 3.1)
576
is fully parsed and processed.
581
<dt id="TermDocumentEnd">document end</dt>
584
The document end of an
585
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG
586
document fragment</span></a> is the time at which the document
587
fragment has been released and is no longer being processed by the
588
<a href="intro.html#TermUserAgent"><span class="svg-term">user agent</span></a>.
592
<dt id="TermDocumentTime">document time</dt>
595
Indicates the position in the timeline relative to the
596
<a href="intro.html#TermDocumentBegin"><span class="svg-term">document begin</span></a>
597
of a given document fragment. Document time is sometimes also referred
598
to as <em>presentation time</em>. For additional information see the
599
SMIL 2.1 definition of
600
<a href="../../2005/REC-SMIL2-20051213/smil-timing.html#Timing-LocalTime">document time</a>
601
([<a href="refs.html#ref-SMIL21">SMIL21</a>], section 10.7.1).
605
<dt id="TermFill">fill</dt>
609
<a href="intro.html#TermPaint"><span class="svg-term">painting</span></a>
610
the interior of a <a href="intro.html#TermShape"><span class="svg-term">shape</span></a>
611
or the interior of the character glyphs in a text string.
615
<dt id="TermFont">font</dt>
618
A font represents an organized collection of
619
<a href="intro.html#TermGlyph"><span class="svg-term">glyphs</span></a>
620
in which the various glyph representations will share a common look
621
or styling such that, when a string of characters is rendered
622
together, the result is highly legible, conveys a particular artistic
623
style and provides consistent inter-character alignment and spacing.
627
<dt id="TermGlyph">glyph</dt>
630
A glyph represents a unit of rendered content within a
631
<a href="intro.html#TermFont"><span class="svg-term">font</span></a>.
632
Often, there is a one-to-one correspondence between characters to be
633
drawn and corresponding glyphs (e.g., often, the character "A" is
634
rendered using a single glyph), but other times multiple
635
glyphs are used to render a single character (e.g., use of
636
accents) or a single glyph can be used to render multiple
637
characters (e.g., ligatures). Typically, a glyph is defined
639
<a href="intro.html#TermShape"><span class="svg-term">shapes</span></a>
640
such as a <a href="paths.html#Introduction">path</a>, possibly with
641
additional information such as rendering hints that help a font engine
642
to produce legible text in small sizes.
646
<dt id="TermGraphicsElement">graphics element</dt>
649
A graphics element is an <a href="intro.html#TermSVGElement"><span class="svg-term">SVG element</span></a> that can cause graphics to be
650
drawn onto the target <a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>. Specifically, the following elements are
652
<a href="multimedia.html#AnimationElement"><span class="code-fragment">'animation'</span></a>,
653
<a href="shapes.html#CircleElement"><span class="code-fragment">'circle'</span></a>,
654
<a href="shapes.html#EllipseElement"><span class="code-fragment">'ellipse'</span></a>,
655
<a href="struct.html#ImageElement"><span class="code-fragment">'image'</span></a>,
656
<a href="shapes.html#LineElement"><span class="code-fragment">'line'</span></a>,
657
<a href="paths.html#PathElement"><span class="code-fragment">'path'</span></a>,
658
<a href="shapes.html#PolygonElement"><span class="code-fragment">'polygon'</span></a>,
659
<a href="shapes.html#PolylineElement"><span class="code-fragment">'polyline'</span></a>,
660
<a href="shapes.html#RectElement"><span class="code-fragment">'rect'</span></a>,
661
<a href="text.html#TextElement"><span class="code-fragment">'text'</span></a>,
662
<a href="text.html#TextAreaElement"><span class="code-fragment">'textArea'</span></a>,
663
<a href="struct.html#UseElement"><span class="code-fragment">'use'</span></a> and
664
<a href="multimedia.html#VideoElement"><span class="code-fragment">'video'</span></a>.
668
<dt id="TermGraphicsReferencingElement">graphics referencing element</dt>
671
A graphics referencing element is a
672
<a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics element</span></a>
673
that uses a reference to a different document or element as the source
674
of its graphical content. The following elements are graphics referencing
676
<a href="multimedia.html#AnimationElement"><span class="code-fragment">'animation'</span></a>,
677
<a href="extend.html#ForeignObjectElement"><span class="element-name">'foreignObject'</span></a>,
678
<a href="struct.html#ImageElement"><span class="code-fragment">'image'</span></a>,
679
<a href="struct.html#UseElement"><span class="code-fragment">'use'</span></a> and
680
<a href="multimedia.html#VideoElement"><span class="code-fragment">'video'</span></a>.
684
<dt id="TermHostLanguage">host language</dt>
687
A host language is a syntax which incorporates one or more
688
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragments</span></a> by inclusion or by reference, and which defines
689
the interactions between document fragments; an example of this is
690
<a href="http://www.w3.org/TR/2007/CR-WICD-20070718/"><cite>WICD Core 1.0</cite></a>,
691
an XML framework which defines how XHTML, SVG, MathML, XForms,
692
SMIL, and other syntaxes interact [<a href="refs.html#ref-WICD">WICD</a>].
696
<dt id="TermInError">in error</dt>
699
A value is in error if it is specifically stated as being "in error"
700
or "an error" in the prose of this specification. See
701
<a href="implnote.html#ErrorProcessing">Error Processing</a> for more
702
detail on handling errors.
706
<dt id="TermInactiveElement">inactive element</dt>
709
An element is inactive when it is outside the active duration or when
710
it is paused. Aural aspects of elements which are inactive (e.g.
711
audio, and the audio track of a video element) are silent. SMIL
712
defines the behavior of inactive elements with respect to timing,
713
events, and hyperlinking. See
714
<a href="../../2005/REC-SMIL2-20051213/smil-timing.html#q174">Modelling interactive, event-based content in SMIL</a>,
715
<a href="../../2005/REC-SMIL2-20051213/smil-timing.html#Timing-PausedElementsAndActiveDur">Paused Elements and Active Duration</a>
716
and <a href="../../2005/REC-SMIL2-20051213/smil-timing.html#Timing-EventSensitivity">Event Sensitivity</a>
717
([<a href="refs.html#ref-SMIL21">SMIL21</a>], sections 10.11.2 and 10.4.3).
721
<dt id="TermIRIReference">IRI reference</dt>
724
An IRI reference is an Internationalized Resource Identifier
725
with an optional fragment identifier, as defined in
726
<a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers</cite></a>
727
[<a href="refs.html#ref-RFC3987">RFC3987</a>].
728
An IRI reference serves as a reference to a resource or (with a
729
fragment identifier) to a secondary resource. See
730
<a href="linking.html#IRIReference">References</a>.
734
<dt id="TermInvalidIRIReference">Invalid IRI reference</dt>
737
An invalid IRI reference is an
738
<a href="intro.html#TermIRIReference"><span class="svg-term">IRI reference</span></a>
739
that is syntactically invalid, cannot be resolved to a resource
740
or takes a form that is not allowed for a given attribute,
741
as defined in <a href="linking.html#ReferenceRestrictions">Reference restrictions</a>.
745
<dt id="TermLacunaValue">lacuna value</dt>
748
A lacuna value is a defined behavior used when an attribute or
749
property is not specified, or when an attribute or property has an
750
<a href="intro.html#TermUnsupportedValue"><span class="svg-term">unsupported value</span></a>.
751
This value is to be used for the purposes of rendering, calculating
752
animation values, and when accessing the attribute or property using
753
the <a href="svgudom.html#svg__TraitAccess"><span class="udom-interface-name">TraitAccess</span></a>
754
interface. As opposed to an XML default value, however, the attribute
755
or property and its value are not visible in the DOM, and cannot be
756
accessed with DOM methods (e.g.
757
<a href="svgudom.html#dom__Element_getAttribute"><span class="dom-method-name">getAttribute</span></a>).
758
For lacunae which are properties, if the property is inherited and
759
there is no inherited value (for example, on the root element), the
761
<a href="http://www.w3.org/TR/CSS2/cascade.html#x1">initial value</a>
762
as specified in the definition of that property
763
([<a href="refs.html#ref-CSS2">CSS2</a>], section 6.1.1).
764
For non-inherited properties, the lacuna value is always the initial value.
767
Note that a lacuna value is distinct from the XML term
768
<a href="http://www.w3.org/TR/xml/#dt-default">default value</a>,
769
which uses DTD lookup to determine whether an attribute is required
770
and what its value is, and inserts required attributes and their
772
([<a href="refs.html#ref-XML10">XML10</a>], section 3.3.2).
773
At the XML parser level, SVG Tiny 1.2 does not have default values;
774
lacunae are part of the SVG application layer, and their values are
779
<dt id="TermLocalIRIReference">local IRI reference</dt>
782
A local IRI reference is an
783
<a href="intro.html#TermIRIReference"><span class="svg-term">IRI reference</span></a>
784
that references a fragment within the same resource. See
785
<a href="linking.html#IRIReference">References</a>.
789
<dt id="TermNavigationAttribute">navigation attribute</dt>
792
A navigation attribute is an XML attribute that specifies the element to
793
be focused when the user instructs the
794
<a href="intro.html#TermSVGUserAgent"><span class="svg-term">SVG user agent</span></a>
795
to navigate the focus in a particular direction or to set the focus to
796
the next or previous element in the focus ring. Specifically, the
797
following attributes are navigation attributes:
798
<a href="interact.html#NavNextAttribute"><span class="attr-name">'nav-next'</span></a>,
799
<a href="interact.html#NavPrevAttribute"><span class="attr-name">'nav-prev'</span></a>,
800
<a href="interact.html#NavUpAttribute"><span class="attr-name">'nav-up'</span></a>,
801
<a href="interact.html#NavDownAttribute"><span class="attr-name">'nav-down'</span></a>,
802
<a href="interact.html#NavLeftAttribute"><span class="attr-name">'nav-left'</span></a>,
803
<a href="interact.html#NavRightAttribute"><span class="attr-name">'nav-right'</span></a>,
804
<a href="interact.html#NavUpLeftAttribute"><span class="attr-name">'nav-up-left'</span></a>,
805
<a href="interact.html#NavUpRightAttribute"><span class="attr-name">'nav-up-right'</span></a>,
806
<a href="interact.html#NavDownLeftAttribute"><span class="attr-name">'nav-down-left'</span></a>
807
and <a href="interact.html#NavDownRightAttribute"><span class="attr-name">'nav-down-right'</span></a>.
808
See <a href="interact.html#specifyingnavigation">Specifying navigation</a>.
812
<dt id="TermNonLocalIRIReference">non-local IRI reference</dt>
815
A non-local IRI reference is an
816
<a href="intro.html#TermIRIReference"><span class="svg-term">IRI reference</span></a>
817
that references a different document or an element within a different
822
<dt id="TermMediaElement">media element</dt>
825
A media element is an element which defines its own timeline within
826
its own time container. The following elements are media elements:
827
<a href="multimedia.html#AnimationElement"><span class="element-name">'animation'</span></a>,
828
<a href="multimedia.html#AudioElement"><span class="element-name">'audio'</span></a> and
829
<a href="multimedia.html#VideoElement"><span class="element-name">'video'</span></a>.
830
See <a href="multimedia.html#multimedia">Multimedia</a>.
834
<dt id="TermPaint">paint</dt>
837
A paint represents a way of putting color values onto the
838
<a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>. A paint might consist of both color values and
839
associated alpha values which control the blending of colors
840
against already existing color values on the <a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>. SVG Tiny 1.2
841
supports two types of built-in paint:
842
<a href="painting.html#Color">color</a> and
843
<a href="painting.html#Gradients">gradients</a>.
847
<dt id="TermPresentationAttribute">presentation attribute</dt>
850
A presentation attribute is an XML attribute on an <a href="intro.html#TermSVGElement"><span class="svg-term">SVG element</span></a> which
851
specifies a value for a given property for that element.
852
See <a href="styling.html">Styling</a>.
856
<dt id="TermProperty">property</dt>
859
A property is a parameter that helps specify how a document should be
860
rendered. A complete list of the SVG properties can be found in the
861
<a href="attributeTable.html">Attribute and Property Table</a> appendix.
862
Properties are assigned to elements in the SVG language by
863
<a href="intro.html#TermPresentationAttribute"><span class="svg-term">presentation attributes</span></a>.
864
See <a href="styling.html">Styling</a>.
868
<dt id="TermRenderingTree">rendering tree</dt>
871
The rendering tree is the set of elements being rendered, aurally or
872
visually using the painters model, in an
873
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>.
874
The following elements in the fragment and their children are part
876
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>,
877
but <em>not</em> part of the rendering tree (and thus are not rendered):
881
<a href="struct.html#DefsElement"><span class="element-name">'defs'</span></a>,
882
<a href="struct.html#DiscardElement"><span class="element-name">'discard'</span></a>,
883
<a href="fonts.html#FontElement"><span class="element-name">'font'</span></a>,
884
<a href="script.html#HandlerElement"><span class="element-name">'handler'</span></a>,
885
<a href="painting.html#LinearGradientElement"><span class="element-name">'linearGradient'</span></a>,
886
<a href="script.html#ListenerElement"><span class="element-name">'listener'</span></a>,
887
<a href="metadata.html#MetadataElement"><span class="element-name">'metadata'</span></a>,
888
<a href="animate.html#MpathElement"><span class="element-name">'mpath'</span></a>,
889
<a href="struct.html#PrefetchElement"><span class="element-name">'prefetch'</span></a>,
890
<a href="painting.html#RadialGradientElement"><span class="element-name">'radialGradient'</span></a>,
891
<a href="script.html#ScriptElement"><span class="element-name">'script'</span></a> or
892
<a href="painting.html#SolidColorElement"><span class="element-name">'solidColor'</span></a>
895
<a href="painting.html#DisplayProperty"><span class="prop-name">'display'</span></a>
896
property is set to <span class="attr-value">'none'</span></li>
897
<li>elements with one or more
898
<a href="intro.html#TermConditionalProcessingAttribute"><span class="svg-term">conditional processing attributes</span></a>
899
that evaluate to false</li>
900
<li>direct children of a
901
<a href="struct.html#SwitchElement"><span class="element-name">'switch'</span></a>
902
element, other than the child that evaluates to true</li>
903
<li><a href="intro.html#TermAnimationElement"><span class="svg-term">animation elements</span></a></li>
906
The copies of elements referenced by a
907
<a href="struct.html#UseElement"><span class="element-name">'use'</span></a>
908
element, on the other hand, are <em>not</em> in the
909
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>
910
but are in the rendering tree. Note that elements with zero opacity,
911
or no <a href="painting.html#FillProperty"><span class="prop-name">'fill'</span></a>
912
and no <a href="painting.html#StrokeProperty"><span class="prop-name">'stroke'</span></a>,
913
or with an <a href="multimedia.html#AudioLevelProperty"><span class="prop-name">'audio-level'</span></a> of zero,
914
or with the <a href="painting.html#VisibilityProperty"><span class="prop-name">'visibility'</span></a>
915
property set to <span class="prop-value">hidden</span>, <em>are</em> still in the rendering tree.
919
<dt id="TermRootmostSVGElement">rootmost 'svg' element</dt>
923
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
924
element is the furthest
925
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
926
ancestor element that does not exit an
927
<a href="intro.html#TermSVGContext"><span class="svg-term">SVG context</span></a>.
930
Note that this definition has been carefully chosen to be applicable not
931
only to SVG Tiny 1.2 (where the rootmost
932
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
933
element is the only <a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
934
element, except when there is an
935
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
937
<a href="extend.html#ForeignObjectElement"><span class="element-name">'foreignObject'</span></a>)
938
but also for SVG Full 1.2 and SVG that uses XBL
939
[<a href="refs.html#ref-XBL2">XBL2</a>]. See also
940
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>.
944
<dt id="TermShadowTree">shadow tree</dt>
947
A tree fragment that is not part of the DOM tree, but which is attached to a referencing element (e.g. <a href="struct.html#UseElement"><span class="code-fragment">'use'</span></a> element) in a non-parent-child relationship, for the purpose of rendering and event propagation. The shadow tree is composed as if it were deep-structure clone of the referenced element in the <a href="intro.html#TermRenderingTree"><span class="svg-term">rendering tree</span></a>. The shadow tree is kept in synchronization with the contents of the referenced element, so that any animation, DOM manipulation, or non-DOM interactive state occurring on the referenced element are also applied to all the referencing instances. In SVG Tiny 1.2, only a subset of all SVG DOM methods to access the shadow tree are available.
950
Also referred to as an "instance tree".
954
<dt id="TermShape">shape</dt>
957
A shape is a <a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics element</span></a>
958
that comprises a defined combination of straight lines and curves.
959
Specifically, the following elements are shapes:
960
<a href="shapes.html#CircleElement"><span class="element-name">'circle'</span></a>,
961
<a href="shapes.html#EllipseElement"><span class="element-name">'ellipse'</span></a>,
962
<a href="shapes.html#LineElement"><span class="element-name">'line'</span></a>,
963
<a href="paths.html#PathElement"><span class="element-name">'path'</span></a>,
964
<a href="shapes.html#PolygonElement"><span class="element-name">'polygon'</span></a>,
965
<a href="shapes.html#PolylineElement"><span class="element-name">'polyline'</span></a> and
966
<a href="shapes.html#RectElement"><span class="element-name">'rect'</span></a>.
970
<dt id="TermStroke">stroke</dt>
973
Stroking is the operation of
974
<a href="intro.html#TermPaint"><span class="svg-term">painting</span></a>
975
the outline of a <a href="intro.html#TermShape"><span class="svg-term">shape</span></a>
976
or the outline of character glyphs in a text string.
980
<dt id="TermSVGContext">SVG context</dt>
983
An SVG context is a document fragment where all elements within the
984
fragment must be subject to processing by an <a href="intro.html#TermSVGUserAgent"><span class="svg-term">SVG user agent</span></a> according
985
to the rules in this specification.
988
If SVG content is embedded inline within parent XML (such as XHTML),
989
the SVG context does not include the ancestors above the
990
<a href="intro.html#TermRootmostSVGElement"><span class="svg-term">rootmost 'svg' element</span></a>.
991
If the SVG content contains any
992
<a href="extend.html#ForeignObjectElement"><span class="element-name">'foreignObject'</span></a>
993
elements which in turn contain non-SVG content, the SVG context does
994
not include the contents of the
995
<a href="extend.html#ForeignObjectElement"><span class="element-name">'foreignObject'</span></a>
999
In SVG Tiny 1.2, an SVG context contains one
1000
<a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a>.
1004
<dt id="TermSVGDocumentFragment">SVG document fragment</dt>
1007
An SVG document fragment is the XML document sub-tree whose rootmost
1008
element is an <a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a>
1009
element (that is, the
1010
<a href="intro.html#TermRootmostSVGElement"><span class="svg-term">rootmost 'svg' element</span></a>.)
1013
An SVG document fragment consists of either a stand-alone SVG document,
1014
or a fragment of a parent XML document where the fragment is enclosed by the
1015
<a href="intro.html#TermRootmostSVGElement"><span class="svg-term">rootmost 'svg' element</span></a>.
1018
In SVG Tiny 1.2, the SVG document fragment must not contain nested
1019
<a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a> elements.
1020
Nested <a href="struct.html#SVGElement"><span class="element-name">'svg'</span></a> elements are
1021
<a href="implnote.html#UnsupportedProps">unsupported elements</a> and must not be rendered.
1022
Note that document conformance is orthogonal to SVG document fragment conformance.
1025
For further details, see the section on
1026
<a href="conform.html#ConformingSVGDocuments">Conforming SVG Document Fragments</a>.
1030
<dt id="TermSVGElement">SVG element</dt>
1033
An SVG element is an element within the SVG namespace defined by the
1034
SVG language specification.
1038
<dt id="TermSVGUserAgent">SVG user agent</dt>
1040
An SVG user agent is a <a href="intro.html#TermUserAgent"><span class="svg-term">user agent</span></a>
1041
that is able to retrieve and render SVG content.
1044
<dt id="TermSyncbase">syncbase</dt>
1047
The syncbase of an <a href="intro.html#TermAnimationElement"><span class="svg-term">animation element</span></a> timing specifier is the element
1048
whose timing this element is relative to,
1049
<a href="../../2005/REC-SMIL2-20051213/smil-timing.html#Timing-Syncbases">as
1050
defined in SMIL 2.1</a> ([<a href="refs.html#ref-SMIL21">SMIL21</a>], section 10.7.1).
1054
<dt id="TermTextContentElement">text content element</dt>
1057
A text content element is an <a href="intro.html#TermSVGElement"><span class="svg-term">SVG element</span></a> that causes a text string
1058
to be rendered onto the <a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>. The SVG Tiny 1.2 text content
1059
elements are the following:
1060
<a href="text.html#TextElement"><span class="element-name">'text'</span></a>,
1061
<a href="text.html#TextAreaElement"><span class="element-name">'textArea'</span></a> and
1062
<a href="text.html#TSpanElement"><span class="element-name">'tspan'</span></a>.
1066
<dt id="TermTextContentBlockElement">text content block element</dt>
1069
A text content block element is a
1070
<a href="intro.html#TermTextContentElement"><span class="svg-term">text content element</span></a>
1071
that serves as a standalone element for a unit of text, and
1072
which may optionally contain certain child
1073
<a href="intro.html#TermTextContentElement"><span class="svg-term">text content elements</span></a>
1074
(e.g. <a href="text.html#TSpanElement"><span class="element-name">'tspan'</span></a>).
1075
SVG Tiny 1.2 defines two text content block elements:
1076
<a href="text.html#TextElement"><span class="element-name">'text'</span></a>
1077
and <a href="text.html#TextAreaElement"><span class="element-name">'textArea'</span></a>.
1081
<dt id="TermTimedElement">timed element</dt>
1084
A timed element is an element that supports the
1085
<a href="animate.html#TimingAttributes">SVG timing attributes</a>.
1086
The following elements are timed elements:
1087
<a href="multimedia.html#AudioElement"><span class="element-name">'audio'</span></a>,
1088
<a href="animate.html#AnimateElement"><span class="element-name">'animate'</span></a>,
1089
<a href="animate.html#AnimateColorElement"><span class="element-name">'animateColor'</span></a>,
1090
<a href="animate.html#AnimateMotionElement"><span class="element-name">'animateMotion'</span></a>,
1091
<a href="animate.html#AnimateTransformElement"><span class="element-name">'animateTransform'</span></a>,
1092
<a href="multimedia.html#AnimationElement"><span class="element-name">'animation'</span></a>,
1093
<a href="animate.html#SetElement"><span class="element-name">'set'</span></a> and
1094
<a href="multimedia.html#VideoElement"><span class="element-name">'video'</span></a>.
1098
<dt id="TermTransformation">transformation</dt>
1101
A transformation is a modification of the
1102
<a href="intro.html#TermCurrentTransformationMatrix"><span class="svg-term">current transformation matrix (CTM)</span></a>
1103
by providing a supplemental transformation in the form of a set of
1104
simple transformations specifications (such as scaling, rotation or translation)
1105
and/or one or more <a href="intro.html#TermTransformationMatrix"><span class="svg-term">transformation matrices</span></a>.
1106
See <a href="coords.html#EstablishingANewUserSpace">Coordinate system transformations</a>.
1110
<dt id="TermTransformationMatrix">transformation matrix</dt>
1113
A transformation matrix defines the mathematical mapping
1114
from one coordinate system into another using a 3x3 matrix
1115
using the equation <span class="code-fragment">[x' y' 1] =
1116
[x y 1] * matrix</span>. See
1117
<a href="intro.html#TermCurrentTransformationMatrix"><span class="svg-term">current transformation matrix (CTM)</span></a>
1118
and <a href="coords.html#EstablishingANewUserSpace">Coordinate system transformations</a>.
1122
<dt id="TermUnsupportedValue">unsupported value</dt>
1125
An unsupported value is a value that does not conform to this
1126
specification, but is not specifically listed as being
1127
<a href="intro.html#TermInError"><span class="svg-term">in error</span></a>.
1128
See the <a href="implnote.html#UnsupportedProps">Implementation Notes</a>
1129
for more detail on processing unsupported values.
1133
<dt id="TermUserAgent">user agent</dt>
1136
The general definition of a user agent is an application
1137
that retrieves and renders Web content, including text,
1138
graphics, sounds, video, images, and other content types. A
1139
user agent may require additional user agents that handle
1140
some types of content. For instance, a browser may run a
1141
separate program or plug-in to render sound or video. User agents
1142
include graphical desktop browsers, multimedia
1143
players, text browsers, voice browsers; used alone or
1144
in conjunction with assistive technologies
1145
such as screen readers, screen magnifiers, speech synthesizers,
1146
onscreen keyboards, and voice input software
1147
<a href="refs.html#ref-UAAG">[UAAG]</a>.
1150
A user agent may or may not have the ability to retrieve
1151
and render SVG content; however, an
1152
<a href="intro.html#TermSVGUserAgent"><span class="svg-term">SVG user agent</span></a>
1153
must be able to retrieve and render SVG content.
1157
<dt id="TermUserCoordinateSystem">user coordinate system</dt>
1160
In general, a coordinate system defines locations and
1161
distances on the current
1162
<a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>.
1163
The current user coordinate system is the coordinate system that is
1164
currently active and which is used to define how coordinates and
1165
lengths are located and computed, respectively, on the
1166
current <a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>.
1167
See <a href="coords.html#InitialCoordinateSystem">initial user coordinate system</a>
1168
and <a href="coords.html#EstablishingANewUserSpace">Coordinate system transformations</a>.
1172
<dt id="TermUserSpace">user space</dt>
1175
User space is a synonym for
1176
<a href="intro.html#TermUserCoordinateSystem"><span class="svg-term">user coordinate system</span></a>.
1180
<dt id="TermUserUnits">user units</dt>
1183
A coordinate value or length expressed in user units
1184
represents a coordinate value or length in the current
1185
<a href="intro.html#TermUserCoordinateSystem"><span class="svg-term">user coordinate system</span></a>.
1186
Thus, 10 user units represents a length of 10 units in the
1187
current <a href="intro.html#TermUserCoordinateSystem"><span class="svg-term">user coordinate system</span></a>.
1191
<dt id="TermViewport">viewport</dt>
1194
A viewport is a rectangular region within the current
1195
<a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a> onto
1196
which <a href="intro.html#TermGraphicsElement"><span class="svg-term">graphics elements</span></a>
1197
are to be rendered. See the description of the
1198
<a href="coords.html#InitialViewport">initial viewport</a> in the
1199
<a href="coords.html">Coordinate Systems, Transformations and Units</a>
1204
<dt id="TermViewportCoordinateSystem">viewport coordinate system</dt>
1207
In general, a coordinate system defines locations and
1208
distances on the current
1209
<a href="intro.html#TermCanvas"><span class="svg-term">canvas</span></a>.
1210
The <span class="svg-term">viewport coordinate system</span> is the
1211
coordinate system that is active at the start of processing of an
1212
<a href="struct.html#SVGElement"><span class="code-fragment">'svg'</span></a>
1213
element, before processing the optional
1214
<a href="coords.html#ViewBoxAttribute"><span class="attr-name">'viewBox'</span></a>
1215
attribute. In the case of an <a href="intro.html#TermSVGDocumentFragment"><span class="svg-term">SVG document fragment</span></a> that is embedded
1216
within a parent document which uses CSS to manage its layout, then the
1217
viewport coordinate system will have the same orientation and
1218
lengths as in CSS, with the origin at the top-left on the
1219
<a href="intro.html#TermViewport"><span class="svg-term">viewport</span></a>. See
1220
<a href="coords.html#InitialViewport">The initial viewport</a>
1221
and <a href="coords.html#EstablishingANewViewport">Establishing a new viewport</a>.
1225
<dt id="TermViewportSpace">viewport space</dt>
1228
Viewport space is a synonym for
1229
<a href="intro.html#TermViewportCoordinateSystem"><span class="svg-term">viewport coordinate system</span></a>.
1233
<dt id="TermViewportUnits">viewport units</dt>
1236
A coordinate value or length expressed in viewport units
1237
represents a coordinate value or length in the
1238
<a href="intro.html#TermViewportCoordinateSystem"><span class="svg-term">viewport coordinate system</span></a>.
1239
Thus, 10 viewport units represents a length of 10 units in the
1240
<a href="intro.html#TermViewportCoordinateSystem"><span class="svg-term">viewport coordinate system</span></a>.
1245
Note: When this specification uses the term
1246
<em><span class="element-name">'svg'</span> element</em>,
1247
<em><span class="element-name">'path'</span> element</em>, or similar reference to
1248
an <a href="intro.html#TermSVGElement"><span class="svg-term">SVG element</span></a> defined within this specification, it is
1249
referring to the element whose namespace URI is <code>http://www.w3.org/2000/svg</code>
1250
and whose local name is the string in quotes (e.g., "svg" or "path").
1251
An exception to this is the
1252
<a href="script.html#ListenerElement"><span class="element-name">'listener'</span></a>
1253
element, whose namespace URI is <code>http://www.w3.org/2001/xml-events</code>.
1256
<h2 id="howtoreference">1.7 How to reference this specification</h2>
1259
When referencing this specification as a whole or when
1260
referencing a chapter or major section, use the
1261
undated URI, <code>http://www.w3.org/TR/SVGTiny12/</code>,
1262
where possible. This allows the reference to always refer to
1263
the latest version of this specification.
1266
<h2 id="howtouse">1.8 How to use this specification</h2>
1267
<p><em>This section is informative.</em></p>
1270
This specification is meant to serve both as a guide to
1271
authors in creating SVG content, and as a detailed reference
1272
for implementors of browsers, viewers, authoring tools,
1273
content processing tools, and other user agents to
1274
create conforming interoperable implementations for
1275
viewing SVG documents or outputting robust SVG code. It is
1276
not intended as a comprehensive manual for authoring content,
1277
and it is expected that books, tutorials, and other materials
1278
based on this specification will be produced to appeal to
1279
different audiences. It is meant to serve as a definitive
1280
source for authors and users to reference when reporting bugs
1281
and feature requests to implementations.
1284
When reading this specification, in order to gain a complete
1285
understanding of the syntax concepts, readers should reference
1286
the individual definitions for elements, attributes, and
1287
properties, but also consult the
1288
<a href="intro.html#Definitions">definitions list</a>, the
1289
<a href="elementTable.html">element</a>,
1290
<a href="attributeTable.html#AttributeTable">attribute</a>,
1291
<a href="attributeTable.html#PropertyTable">property</a>
1292
tables, and for more technically adept readers, the
1293
<a href="schema.html">RelaxNG schema</a>. For understanding
1294
scripting in SVG, readers should consult the sections on
1295
<a href="interact.html">Interactivity</a>,
1296
<a href="script.html">Scripting</a>, and the
1297
<a href="svgudom.html">SVG Micro DOM (uDOM)</a>.
1301
<div class="footer">
1302
SVG Tiny 1.2 – 20081222
1304
<li><a href="index.html">Top</a></li>
1305
<li><a href="expanded-toc.html">Contents</a></li>
1306
<li><a href="concepts.html">Next</a></li>
1307
<li><a href="elementTable.html">Elements</a></li>
1308
<li><a href="attributeTable.html">Attributes</a></li>
added
removed
www.w3.org/TR/2008/REC-SVGTiny12-20081222/intro.html
