text: Copyright second public draft. A list of changes since the first draft of 30 October 2001 is available.
  1.1.1 Element and Attribute Collections
  1.2 Profiling the SVG specification
  2 Structure
  2.1 The version attribute
  2.2 The baseProfile attribute
  2.3 Full Core Attribute Module
  2.4 Full Structure Module
  2.4.1 Full Structure Content Sets
  2.5 Tiny Structure Module
  2.5.1 Tiny Structure Content Sets
  2.6 Full Container Attribute Module
  2.7 Full Viewport Attribute Module
  3 Coordinate Systems, Transforms and Units
  3.1 Geographic Coordinate System
  3.2 Using Viewport Coordinates
  4 Style
  4.1 Full Style Module
  4.1.1 Full Style Content Set
  4.1.2 Full Style Attribute Set
  5 Painting
  5.1 Full Paint Attribute Module
  5.2 Tiny Paint Attribute Module
  5.3 Full Opacity Attribute Module
  5.4 Full Graphics Attribute Module
  5.5 Tiny Graphics Attribute Module
  6 Hyperlinking
  6.1 Full Hyperlinking Module
  6.1.1 Full Hyperlinking Content Set
  6.2 Full XLink Attribute Module
  6.3 Full ExternalResourcesRequired Attribute Module
  7 Conditional Processing
  7.1 The requiredFeatureList attribute
  7.2 Full Conditional Processing Module
  7.2.1 Full Conditional Processing Content Set
  7.2.2 Full Conditional Processing Attribute Set
  8 Shapes
  8.1 Full Shape Module
  8.1.1 Full Shape Content Set
  9 Images
  9.1 Full Image Module
  9.1.1 Full Image Content Set
  9.1.2 Full Image Attribute Set
  10 Text
  10.1 Simple Text Wrapping
  10.2 Full Text Module
  10.2.1 Full Text Content Sets
  10.2.2 Full Text Attribute Sets
  10.3 Basic Text Module
  10.3.1 Basic Text Content Sets
  10.3.2 Basic Text Attribute Sets
  10.4 Tiny Text Module
  10.4.1 Tiny Text Content Sets
  10.4.2 Tiny Text Attribute Set
  11 Color
  11.1 Color Element
  11.2 Full Color Module
  11.2.1 Full Color Content Set
  11.2.2 Full Color Attribute Set
  11.3 Tiny Color Module
  11.3.1 Tiny Color Attribute Set
  12 Gradients
  12.1 Full Gradient Module
  12.1.1 Full Gradient Content Set
  12.1.2 Full Gradient Attribute Set
  13 Patterns
  13.1 Full Pattern Module
  13.1.1 Full Pattern Content Set
  14 Clipping
  14.1 Full Clip Module
  14.1.1 Full Clip Content Set
  14.1.2 Full Clip Attribute Set
  14.2 Basic Clip Module
  14.2.1 Basic Clip Content Set
  14.2.2 Basic Clip Attribute Set
  15 Masking
  15.1 Full Mask Module
  15.1.1 Full Mask Content Set
  15.1.2 Full Mask Attribute Set
  16 Markers
  16.1 Full Marker Module
  16.1.1 Full Marker Content Set
  16.1.2 Full Marker Attribute Set
  17 Fonts
  17.1 Full Font Module
  17.1.1 Full Font Content Set
  17.2 Tiny Font Module
  17.2.1 Tiny Font Content Set
  18 Interactivity
  18.1 Full Document Events Attribute Module
  18.2 Full Graphical Element Events Attribute Module
  18.3 Full Animation Events Attribute Module
  19 Scripting
  19.1 Full Scripting Module
  19.1.1 Full Scripting Content Set
  20 Cursors
  20.1 Full Cursor Module
  20.1.1 Full Cursor Content Set
  20.1.2 Full Cursor Attribute Set
  21 Views
  21.1 Full View Module
  21.1.1 Full View Content Set
  22 Filters
  22.1 Full Filter Module
  22.1.1 Full Filter Content Sets
  22.1.2 Full Filter Attribute Sets
  22.2 Basic Filter Module
  22.2.1 Basic Filter Content Sets
  22.2.2 Basic Filter Attribute Sets
  23 Animation
  23.1 Full Animation Module
  23.1.1 Full Animation Content Set
  23.1.2 Full Animation Attribute Sets
  24 Extensibility
  24.1 Full Extensibility Module
  24.1.1 Full Extensibility Content Set
  A XML Schema
  B DTD
  C References
  D Author List SVG 1.1 editorial team intended for this draft to be a complete self-contained specification, but this was not possible in the short timeframe. The next version of this document will be a complete self-contained specification..
  Each major section of the SVG 1.0 specification produces a module named after that section, e.g. "Full Text Module". The term "Full" implies that the module includes the complete set of elements and attributes with no restrictions from the corresponding section of the specification. If there is need to provide a subset of the functionality in a Full module, then Basic and/or Tiny modules are created. A Tiny module is a subset of a Basic module which is a subset of a Full module.
  It is an error for a profile of SVG 1.1 to include a module and a subset of that module (e.g. the FullAttrsAll, which is the union of all the presentation attribute collections (i.e. all the attribute collections with the string "Presentation" in their name).
  A subset module (ie. a Basic or Tiny Full modules listed in this specification. Future drafts of this document will include a table that lists all elements, attributes and properties, along with the modules in which they are included.".
  Note:This section is not complete. The idea is for this attribute to be a shorthand for the requiredFeatureList test attribute. The values for this attribute may be restricted in future versions of this specification.
  In the situations where a DOCTYPE declaration is not available, SVG user agents require a method to identify the type of SVG content that the document fragment is using. The baseProfile attribute has been added to the 'svg' element in SVG 1.1 to provide this information. Each profile of SVG is required to define a value to be used for the baseProfile attribute, preferably the name of the profile.
  Indicates the SVG language profile that this document fragment is based on. An SVG user agent is required to minimally support this base profile in order to render the document fragment correctly.
  The Full Core Attribute Module defines the attribute set StdAttrs that is the core set of attributes that can be present on any element.
  The Full Container Attribute Module defines the ContainerPresentationAttrs attribute set.
  For further details refer to [SVG 1.0] : Chapter 7 - Coordinate Systems
  In order to allow interoperability between SVG content generators and user agents dealing with maps encoded in SVG, the SVG 1.1 specification encourages the use of a common metadata definition for describing the coordinate system used in the SVG files.
  These metadata should be added under the 'metadata' element of the topmost 'svg' element describing the map. They consists of an RDF description of the Coordinate Reference System definition of the SVG map.
  The definition should be conformant to the XML grammar described in the OpenGIS Recommendation on the Definition of Coordinate Reference System [OpenGIS Coordinate Systems]. In order to correctly map the 2-dimensional data used by SVG, the CRS must be of subtype ProjectedCRS or Geographic2dCRS. The first axis of the described CRS maps the x-axis and the second axis maps the y-axis.
  The main interest of such metadata is to indicate to the User Agent that two or more SVG documents can be overlayed or merged into a single document. Obviously, if two maps reference the same Coordinate Reference System definition then they can be overlayed without reprojecting the data. If the maps reference different Coordinate Reference Systems, then a specialised cartographic User Agent may choose to transform the coordinate data to overlay the data. However, typical SVG user agents are not required to perform these types of transformations, or even recognise the metadata.
  Below are two examples of the coordinate metadata.
  <svg ...> <metadata> <rdf:RDF xmlns: <rdf:Description> <!-- The Coordinate Reference System is described through an URI. Is that legal RDF/XML??? --> <crs:CoordinateReferenceSystem rdf: </rdf:Description> </rdf:RDF> </metadata> <!-- The actual map content --> </svg> <svg ...> <metadata> <rdf:RDF xmlns: <rdf:Description> <!-- In case of a well-known Coordinate Reference System an 'Identifier' is enough to describe the CRS --> <crs:CoordinateReferenceSystem>  SVG Working Group considered adding the ability to allow graphical elements to be described using viewport coordinates into SVG 1.1. With this feature, graphical content such as toolbars or map legends could be statically placed within the user agent viewport and be unaffected by zoom and pan.
  While the benefits of such a feature are obvious, the Working Group has decided to leave this feature out of SVG 1.1 and consider it for SVG 2.0. There are two reasons behind the decision: a substantial change to the rendering and coordinate system model is inappropriate for a minor update of the SVG specification and that the feature is difficult to describe and implement, and thus warrants heavy consideration to ensure the most appropriate solution is found.
  For further details refer to [SVG 1.0] : Chapter 6 - Styling
  For further details refer to [SVG 1.0] : Chapter 11 - Painting: Filling, Stroking and Marker Symbols
  The Full Paint Attribute Module defines the PaintPresentationAttrs attribute set.
  The Tiny Paint Attribute Module defines the PaintPresentationAttrs attribute set.
  The Full Opacity Attribute Module defines the OpacityPresentationAttrs attribute set.
  The Full Graphics Attribute Module defines the GraphicsPresentationAttrs attribute set.
  For further details refer to [SVG 1.0] : Chapter 17 - Linking
  The Full XLink Attribute Module defines the XLinkRefAttrs attribute set.
  For further details refer to [SVG 1.0] : Chapter 5 - Document Structure : switch element
  Note:This section is not complete.
  SVG 1.1 will deprecate the requiredFeatures and requiredExtensions attributes and replace them with requiredFeatureList. This attribute will allow boolean logic expressions based on XPath to allow greater control over conditional processing. There will be a mapping from the deprecated syntax to the new syntax.
  The feature strings used SVG 1.1 will be URIs.
  The Full Conditional Processing Module defines the ConditionalElements content set.
  For further details refer to [SVG 1.0] : Chapter 8 - Paths and Chapter 9 - Basic Shapes
  For further details refer to [SVG 1.0] : Chapter 5 - Document Structure : image Element
  For further details refer to [SVG 1.0] : Chapter 10 - Text
  Note:This section is not complete and is still under discussion. It is included here in its present form to give both implementors and users the earliest opportunity to provide feedback.
  SVG 1.1 will include new elements to support simple text wrapping, as shown in the example below.
  <tblock> <!-- You can specify regions inline via <region> or reference via <regionRef>. By default, </region> <regionRef xlink: <flow> <p> My initial paragraph has a <span fill="red">RED</span> word, and has these other words, also. </p> <!-- Note the <br/> element below --> <p> <span>Second<br/>paragraph.</span> </p> </flow> </tblock>
  There will be seven new elements: 'tblock', 'region', 'regionRef', 'flow', 'p', 'span' and 'br'. All will be included in the Full Text Module and the Basic Text Module, but not the Tiny Text Module.
  Note:Alternatively, there may be a separate Text Wrapping Module.
  Each 'tblock' has at least one 'region' child to define the area in which text wrapping will occur. If multiple regions are defined, then once a region is filled the text will flow into the next region. The text to wrap is defined in the 'flow' element.
  The default user agent style sheet for SVG 1.1 will specify 'p' as a block element, 'span' as an inline element and 'br' as a forced linebreak. When elements from arbitrary namespaces are inserted in a 'flow' element, the content of those elements will be wrapped according to the value of their display property. The SVG user agent will position the text based on the properties, not the elements or their tag names.
  The algorithm for line breaking will be very simple, basically breaking on spaces, zero-width spaces and Unicode soft hypens. If it is necessary to break a line that does not have any of these characters, then the line will break after the last character that fits. The algorithm will support multiline bidirectional text. The algorithm will produce identical results across implementations when the text is rendered with an SVG font.
  The Full Text Module defines the TextElements and TextContentElements content sets.
  The Basic Text Module defines the TextElements and TextContentElements content sets.
  For further details refer to [SVG 1.0] : Chapter 12 - Color
  Note:This section is not complete.
  The next version of this specification will include a element called 'solidColor' that provides a paint server with a solid color fill at a specified opacity. This way, elements can reference a solid fill style in the same manner as used for the other paint servers, gradients and patterns.
  For further details refer to [SVG 1.0] : Chapter 13 - Gradients and Patterns
  For further details refer to [SVG 1.0] : Chapter 13 - Gradients and Patterns 20 - Fonts
  For further details refer to [SVG 1.0] : Chapter 16 - Interactivity
  The Full Document Events Attribute Module defines the DocumentEventsAttrs attribute set.
  The Full Graphical Element Events Attribute Module defines the GraphicalElementEventsAttrs attribute set.
  For further details refer to [SVG 1.0] : Chapter 18 - Scripting
  For further details refer to [SVG 1.0] : Chapter 16 - Interactivity
  For further details refer to [SVG 1.0] : Chapter 16 - Interactivity
  For further details refer to [SVG 1.0] : Chapter 15 - Filters
  The Full Filter Module defines the FilterElements and FilterPrimitiveElements content sets.
  The Basic Filter Module defines the FilterElements and FilterPrimitiveElements content sets.
  For further details refer to [SVG 1.0] : Chapter 19 - Animation
  The Full Animation Module defines the AnimationElements content set.
  For further details refer to [SVG 1.0] : Chapter 23 - Extensibility
  Note:This schema is still in development and is being tested. The SVG Working Group welcomes feedback on this topic.
  The XML Schema for SVG 1.1 is available at:
  The schema references the following files: and.