Remove references to DTDs.
--- a/master/animate.html Thu May 17 18:01:13 2012 +1000
+++ b/master/animate.html Thu May 17 19:22:29 2012 +1000
@@ -194,8 +194,6 @@
<pre><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="8cm" height="3cm" viewBox="0 0 800 300"
xmlns="http://www.w3.org/2000/svg" version="1.1">
<desc>Example anim01 - demonstrate animation elements</desc>
@@ -612,8 +610,8 @@
defined relative to the time that the event is raised.
The list of event-symbols available for a given
event-base element is the list of event attributes
- available for the given element as defined by the <a
- href="svgdtd.html">SVG DTD</a>, with the one difference
+ available for the given element as defined in the <a
+ href="interact.html">Interactivity</a> chapter, with the one difference
that the leading 'on' is removed from the event name
(i.e., the animation event name is 'click', not
'onclick'). A list of all events supported by SVG can
@@ -1733,8 +1731,6 @@
a triangle moving along a motion path.</p>
<pre><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="5cm" height="3cm" viewBox="0 0 500 300"
xmlns="http://www.w3.org/2000/svg" version="1.1"
xmlns:xlink="http://www.w3.org/1999/xlink" >
@@ -2298,8 +2294,6 @@
<pre><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="4cm" height="2cm" viewBox="0 0 400 200"
xmlns="http://www.w3.org/2000/svg"
onload="StartAnimation(evt)" version="1.1">
--- a/master/changes.html Thu May 17 18:01:13 2012 +1000
+++ b/master/changes.html Thu May 17 19:22:29 2012 +1000
@@ -35,10 +35,11 @@
<p>In additional to the editorial changes listed above, the following substantial additions, changes and removals
have been made.</p>
-<!--
<h3 id="whole">Across the whole document</h3>
--->
+<ul>
+ <li>References to the SVG DTD have been removed.</li>
+</ul>
<h3 id="text">Text chapter</h3>
@@ -74,5 +75,11 @@
Filter Effect specification.</li>
</ul>
+<h3 id="svgdtd">Document Type Definition appendix</h3>
+
+<ul>
+ <li>Removed this appendix, as SVG 2.0 is not defined in terms of a DTD.</li>
+</ul>
+
</body>
</html>
--- a/master/conform.html Thu May 17 18:01:13 2012 +1000
+++ b/master/conform.html Thu May 17 19:22:29 2012 +1000
@@ -44,31 +44,16 @@
<a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/"><cite>Cascading Style Sheets, level 2</cite></a>
[<a href="refs.html#ref-CSS2">CSS2</a>],</li>
- <li>any <code><?xml-stylesheet?></code> processing instruction conforms to
+ <li>and any <code><?xml-stylesheet?></code> processing instruction conforms to
<a href="http://www.w3.org/1999/06/REC-xml-stylesheet-19990629/"><cite>Associating stylesheets with XML documents</cite></a>
[<a href='refs.html#ref-XML-SS'>XML-SS</a>],</li>
+</ul>
- <li>and the document fragment is determined to be valid as follows:
- <ol>
- <li>Let <var>E</var> be the encoding of the XML document in which the SVG document fragment resides.</li>
- <li>Let <var>V</var> be the XML version of the document in which the SVG document fragment resides.</li>
- <li>Let <var>D</var> be an XML document constructed by concatenating:
- <ul>
- <li>an XML declaration identifying version <var>V</var> and encoding <var>E</var> (that is, <code><?xml version="<var>V</var>" encoding="<var>E</var>"?></code>),</li>
- <li>the DOCTYPE declaration <code><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" SYSTEM "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"></code>, and</li>
- <li>the SVG document fragment with any entities expanded.</li>
- </ul>
- </li>
- <li>Remove from <var>D</var> any subtree rooted by an element that is not in the SVG namespace.</li>
- <li>Remove from <var>D</var> any attribute that is in a namespace that is not the XLink namespace or the Namespaces in XML namespace.</li>
- <li>Remove the prefix from the name of any element in <var>D</var> that uses one.</li>
- <li>Let <var>A</var> be the set of all attributes in <var>D</var> that are in the XLink namespace.</li>
- <li>Set the attributes <span class='attr-value'>xmlns="http://www.w3.org/2000/svg"</span> and <span class='attr-value'>xmlns:xlink="http://www.w3.org/1999/xlink"</span> on <var>D</var>'s document element and remove any other attributes in the Namespaces in XML namespace from <var>D</var>.</li>
- <li>Change the prefix of every attribute <var>A</var> to be <code>xlink</code>.</li>
- <li>The document fragment is valid if <var>D</var> is a <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#dt-valid">valid XML document</a> ([<a href='refs.html#ref-XML10'>XML10</a>], section 2.8).</li>
- </ol>
- </li>
-</ul>
+<p class='issue'>We will need to have some normative requirements throughout the
+spec that certain elements be allowed only as children of other elements, and
+similarly for attributes. This is in place of the previous check for validity
+against the DTD that used to be part of the <em>conforming SVG Document Fragment</em>
+definition.</p>
<p>SVG document fragments can be included within parent XML documents using
the XML namespace facilities described in
--- a/master/coords.html Thu May 17 18:01:13 2012 +1000
+++ b/master/coords.html Thu May 17 19:22:29 2012 +1000
@@ -648,8 +648,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="300px" height="200px" version="1.1"
viewBox="0 0 1500 1000" preserveAspectRatio="none"
xmlns="http://www.w3.org/2000/svg">
@@ -715,8 +713,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="300px" height="200px" version="1.1"
xmlns="http://www.w3.org/2000/svg">
<strong><g transform="scale(0.2)"></strong>
@@ -734,8 +730,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="150px" height="200px" version="1.1"
xmlns="http://www.w3.org/2000/svg">
<strong><g transform="scale(0.1 0.2)"></strong>
@@ -1038,8 +1032,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="4in" height="3in" version="1.1"
xmlns="http://www.w3.org/2000/svg">
<desc>This SVG drawing embeds another one,
--- a/master/extend.html Thu May 17 18:01:13 2012 +1000
+++ b/master/extend.html Thu May 17 19:22:29 2012 +1000
@@ -222,77 +222,6 @@
transformations and compositing. At this time, such a
capability is not a requirement.</p>
-<h2 id="PrivateElementsAndAttribute">Adding private elements and attributes to the DTD</h2>
-
-<p>Using foreign namespaces as an extension mechanism adds flexibility, is
-readily handled by validation technologies like NVDL and RelaxNG, but typically
-breaks DTD validation unless the DTD has explicit extensibility hooks.</p>
-
-<p>The SVG DTD allows for extending the SVG language within the
-internal DTD subset. Within the internal DTD subset, you have
-the ability to add custom elements and attributes to most SVG
-elements. This facility may be used if DTD validation is desired.</p>
-
-<p>The DTD defines an extension entity for most of SVG
-elements. For example, the <a>'view'</a> element is defined in
-the DTD as follows:</p>
-
-<pre class="dtd-fragment"><![CDATA[
-<!ENTITY % SVG.view.extra.content "" >
-
-<!ENTITY % SVG.view.element "INCLUDE" >
-<![%SVG.view.element;[
-<!ENTITY % SVG.view.content
- "( %SVG.Description.class; %SVG.view.extra.content; )*"
->
-<!ELEMENT %SVG.view.qname; %SVG.view.content; >
-<!-- end of SVG.view.element -->]]>]]><![CDATA[
-
-<!ENTITY % SVG.view.attlist "INCLUDE" >
-<![%SVG.view.attlist;[
-<!ATTLIST %SVG.view.qname;
- %SVG.Core.attrib;
- %SVG.External.attrib;
- viewBox %ViewBoxSpec.datatype; #IMPLIED
- preserveAspectRatio %PreserveAspectRatioSpec.datatype; 'xMidYMid meet'
- zoomAndPan ( disable | magnify ) 'magnify'
- viewTarget CDATA #IMPLIED
->
-<!-- end of SVG.view.attlist -->]]>]]>
-</pre>
-
-<p>The entity <code>SVG.view.extra.content</code> can be defined in the
-internal DTD subset to add custom sub-elements
-attributes to the <a>'view'</a> element within a given
-document, and an <code><!ATTLIST></code> can be used to add
-custom attributes. For example, the following extends the <a>'view'</a> element with an
-additional child element <span
-class="element-name">'customNS:customElement'</span> and an
-additional attribute <span class="attr-name">'customNS:customAttr'</span>:</p>
-
-<pre><![CDATA[
-<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd" [
-<!ENTITY % SVG.view.extra.content "| customNS:customElement" >
-<!ATTLIST %SVG.view.qname;
- xmlns:customNS CDATA #FIXED "http://www.example.org/customNS"
- customNS:customAttr CDATA #IMPLIED>
-<!ELEMENT customNS:customElement EMPTY>
-<!ATTLIST customNS:customElement
- xmlns:customNS CDATA #FIXED "http://www.example.org/customNS"
- info CDATA #IMPLIED>
-]>
-<svg xmlns="http://www.w3.org/2000/svg" version="1.1"
- width="8cm" height="4cm">
- <desc>Extend the 'view' element via the internal DTD subset</desc>
- <!-- Presumably, some great graphics would go here. -->
- <view viewBox="100 110 20 30" customNS:customAttr="123">
- <customNS:customElement info="abc"/>
- </view>
-</svg>
-]]></pre>
-
<h2 id="DOMInterfaces">DOM interfaces</h2>
<h3 id="InterfaceSVGForeignObjectElement">Interface SVGForeignObjectElement</h3>
--- a/master/implnote.html Thu May 17 18:01:13 2012 +1000
+++ b/master/implnote.html Thu May 17 19:22:29 2012 +1000
@@ -31,11 +31,13 @@
specification</a> [<a href="refs.html#ref-XML10">XML10</a>], such as the
use of incorrect XML syntax</li>
- <li>When an element or attribute is encountered in the
- document which is not part of the <a href="svgdtd.html">SVG DTD</a>
- and which is not properly identified as being part of
- another namespace (see <a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/"><cite>Namespaces in XML</cite></a>
- [<a href="refs.html#ref-XML-NS">XML-NS</a>])</li>
+ <li>When an element in the SVG namespace is encountered which is not listed
+ as being a valid child of its parent according to the parent element's
+ definition</li>
+
+ <li>When an attribute in no namespace is encountered on an SVG element,
+ and the attribute is not listed as being a valid attribute for that element
+ according to the element's definition</li>
<li>When an element has an attribute or property value which
is not permissible according to this specification</li>
@@ -108,32 +110,16 @@
<h2 id="VersionControl">Version control</h2>
-<p>The SVG user agent must verify the reference to the PUBLIC
-identifier in the <code><!DOCTYPE></code> statement or
-the namespace reference in the <span class='attr-name'>'xmlns'</span> attribute on
-the <a>'svg'</a> element to ensure that
-the given document (or document fragment) identifies a version
-of the SVG language which the SVG user agent supports. If the
-version information is missing or the version information
-indicates a version of the SVG language which the SVG user
-agent does not support, then the SVG user agent is not required
-to render that document or fragment. In particular, it is not
-required that an SVG user agent attempt to render future
-versions of the SVG language. If the user environment provides
-such an option, the user agent should alert or otherwise notify
-the user that the version of the file is not supported and
-suggest an alternate processing option (e.g., installing an
-updated version of the user agent) if such an option
-exists.</p>
-
-<p>An SVG user agent which supports the SVG Recommendation
-should alert or otherwise notify the user whenever it
-encounters an SVG document (or document fragment) whose
-<code><!DOCTYPE></code> statement or corresponding
-<span class='attr-name'>'xmlns'</span> attribute corresponds to a working draft
-version of the SVG specification. All content based on working
-drafts of this specification should be updated to the SVG
-Recommendation.</p>
+<p class='issue'>Here we previously required SVG user agents to
+check the PUBLIC identifier in a DOCTYPE declaration or the
+"version" of the SVG language as represented by the namespace
+to verify that it understands the version of SVG the document
+was authored against. It also had wording about not needing
+to render future specification's elements, and for a UA to
+alert the user if it encounters a version it doesn't recognise.
+This should all be replaced with some wording about how to
+process elements the UA recognises and those that it doesn't,
+without any reference to versions of the specification.</p>
<h2 id="RangeClamping">Clamping values which are restricted to a particular range</h2>
--- a/master/intro.html Thu May 17 18:01:13 2012 +1000
+++ b/master/intro.html Thu May 17 19:22:29 2012 +1000
@@ -58,11 +58,6 @@
achieving greater accessibility, see
<a href="access.html">Accessibility</a>.</p>
-<p>SVG 1.1 is a modularization of SVG 1.0 [<a href='refs.html#ref-SVG10'>SVG10</a>].
-See the <a href="svgdtd.html">Document Type Definition</a> appendix for
-details on how the DTD is structured to allow profiling and composition with
-other XML languages.</p>
-
<h2 id="MIMEType">SVG MIME type, file name extension and Macintosh file type</h2>
<p>The MIME type for SVG is "<tt>image/svg+xml</tt>" (see
@@ -84,41 +79,19 @@
SVG files stored on Macintosh HFS file systems be given a file
type of <code>"svgz"</code> (all lowercase).</p>
-<h2 id="NamespaceAndDTDIdentifiers">SVG Namespace, Public Identifier and System Identifier</h2>
-
-<p>The following are the SVG 1.1 namespace, public identifier
-and system identifier:</p>
-
-<dl>
- <dt id="Namespace">SVG Namespace:</dt>
- <dd>http://www.w3.org/2000/svg</dd>
- <dt id="PublicID">Public Identifier for SVG 1.1:</dt>
- <dd>PUBLIC "-//W3C//DTD SVG 1.1//EN"</dd>
- <dt id="SystemID">System Identifier for the SVG 1.1 Recommendation:</dt>
- <dd>http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd</dd>
-</dl>
+<div class="ready-for-wg-review">
+<h2 id="Namespace">SVG Namespace</h2>
-<p>The following is an example <a
-href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-prolog-dtd">document
-type declaration</a> for an SVG document:</p>
-
-<pre>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
-</pre>
+<p>The SVG 2.0 namespace is <code>http://www.w3.org/2000/svg</code>,
+which is the same as for earlier versions of SVG.</p>
-<p>Note that DTD listed in the System Identifier is a
-modularized DTD (i.e. its contents are spread over multiple
-files), which means that a validator may have to fetch the
-multiple modules in order to validate. For that reason,
-there is a single flattened DTD available that corresponds
-to the SVG 1.1 modularized DTD. It can be found at
-<a href="http://www.w3.org/Graphics/SVG/1.1/DTD/svg11-flat.dtd">http://www.w3.org/Graphics/SVG/1.1/DTD/svg11-flat.dtd</a>.</p>
+<h2 id="DTD">DTD</h2>
-<p>While a DTD is provided in this specification, the use of DTDs for
+<p>A DTD is not provided in this specification, as the use of DTDs for
validating XML documents is known to be problematic. In particular, DTDs
-do not handle namespaces gracefully. It is <em>not</em> recommended that
-a DOCTYPE declaration be included in SVG documents.</p>
+do not handle namespaces gracefully. It is recommended that authors
+do not include a DOCTYPE declaration in SVG documents.</p>
+</div>
<h2 id="W3CCompatibility">Compatibility with Other Standards Efforts</h2>
--- a/master/metadata.html Thu May 17 18:01:13 2012 +1000
+++ b/master/metadata.html Thu May 17 19:22:29 2012 +1000
@@ -68,16 +68,15 @@
stand-alone SVG document. The <a>'metadata'</a> child element to an <a>'svg'</a> element serves the
purposes of identifying document-level metadata.</p>
-<p>The DTD definitions of many of SVG's elements (particularly,
+<p>The definitions of many of SVG's elements (particularly,
container and text elements) place no restriction on the
placement or number of the <a>'metadata'</a> sub-elements. This
flexibility is only present so that there will be a consistent
content model for container elements, because some container
elements in SVG allow for mixed content, and because <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-mixed-content">the mixed
content rules for XML</a> ([<a href="refs.html#ref-XML10">XML10</a>], section 3.2.2)
-do not permit the desired restrictions. Representations of
-future versions of the SVG language might use more expressive
-representations than DTDs which allow for more restrictive
+do not permit the desired restrictions. Future
+versions of the SVG language might provide more restrictive
mixed content rules. It is strongly recommended that at most
one <a>'metadata'</a> element appear
as a child of any particular element, and that this element
--- a/master/painting.html Thu May 17 18:01:13 2012 +1000
+++ b/master/painting.html Thu May 17 19:22:29 2012 +1000
@@ -1582,8 +1582,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="4in" height="2in"
viewBox="0 0 4000 2000" version="1.1"
xmlns="http://www.w3.org/2000/svg">
@@ -1611,8 +1609,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="4in" height="2in"
viewBox="0 0 4000 2000" version="1.1"
xmlns="http://www.w3.org/2000/svg">
--- a/master/script.html Thu May 17 18:01:13 2012 +1000
+++ b/master/script.html Thu May 17 19:22:29 2012 +1000
@@ -93,8 +93,6 @@
<pre class="xml"><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="6cm" height="5cm" viewBox="0 0 600 500"
xmlns="http://www.w3.org/2000/svg" version="1.1">
<desc>Example script01 - invoke an ECMAScript function from an onclick event
--- a/master/struct.html Thu May 17 18:01:13 2012 +1000
+++ b/master/struct.html Thu May 17 19:22:29 2012 +1000
@@ -300,8 +300,6 @@
<pre class='xml'><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg"
version="1.1" width="4in" height="3in">
<desc>Groups can nest</desc>
@@ -447,7 +445,6 @@
<pre><![CDATA[
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg SYSTEM "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg"
version="1.1" width="4in" height="3in">
<g>
@@ -493,7 +490,7 @@
available to users. The mechanism for doing so depends on the user agent
(e.g., as a caption, spoken).</p>
-<p>The DTD definitions of many of SVG's elements (particularly,
+<p>The definitions of many of SVG's elements (particularly,
container and text elements) place no restriction on the
placement or number of the <a>'desc'</a> and <a>'title'</a> sub-elements.
This flexibility is only present so that there will be a consistent
@@ -501,9 +498,8 @@
elements in SVG allow for mixed content, and because
<a href="http://www.w3.org/TR/2008/REC-xml-20081126/#sec-mixed-content">the mixed content rules for XML</a>
([<a href="refs.html#ref-XML10">XML10</a>], section 3.2.2)
-do not permit the desired restrictions. Representations of
-future versions of the SVG language might use more expressive
-representations than DTDs which allow for more restrictive
+do not permit the desired restrictions. Future
+versions of the SVG language might have more restrictive
mixed content rules. It is strongly recommended that at most
one <a>'desc'</a> and at most one <a>'title'</a> element appear as a
child of any particular element, and that these elements appear
@@ -1025,8 +1021,6 @@
<pre>
<?xml version="1.0" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg width="4in" height="3in" version="1.1"
xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<desc>This graphic links to an external image
--- a/master/style/default_svg.css Thu May 17 18:01:13 2012 +1000
+++ b/master/style/default_svg.css Thu May 17 19:22:29 2012 +1000
@@ -246,6 +246,9 @@
h1.ready-for-wg-review,
h2.ready-for-wg-review,
h3.ready-for-wg-review,
+.ready-for-wg-review > h1,
+.ready-for-wg-review > h2,
+.ready-for-wg-review > h3,
.ready-for-wg-review {
background-color: #FBFBB6 ! important;
}
@@ -258,6 +261,9 @@
h1.ready-for-wider-review,
h2.ready-for-wider-review,
h3.ready-for-wider-review,
+.ready-for-wider-review > h1,
+.ready-for-wider-review > h2,
+.ready-for-wider-review > h3,
.ready-for-wider-review {
background-color: white ! important;
}
--- a/master/styling.html Thu May 17 18:01:13 2012 +1000
+++ b/master/styling.html Thu May 17 19:22:29 2012 +1000
@@ -432,9 +432,7 @@
xmlns:svg="http://www.w3.org/2000/svg">
<xsl:output
method="xml"
- encoding="utf-8"
- doctype-public="-//W3C//DTD SVG 1.1//EN"
- doctype-system="http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"/>
+ encoding="utf-8">
<!-- Add version to topmost 'svg' element -->
<xsl:template match="/svg:svg">
<xsl:copy>
@@ -464,8 +462,6 @@
<strong>SVG content after applying mystyle.xsl</strong>
<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg"
width="10cm" height="5cm" version="1.1">
<rect x="2cm" y="1cm" width="6cm" height="3cm" fill="red" stroke="blue" stroke-width="3"/>
@@ -505,8 +501,6 @@
<strong>SVG file referencing mystyle.css</strong>
<?xml version="1.0" standalone="no"?>
<?xml-stylesheet href="mystyle.css" type="text/css"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1"
width="10cm" height="5cm" viewBox="0 0 1000 500">
<rect x="200" y="100" width="600" height="300"/>
@@ -635,10 +629,8 @@
([<a href="refs.html#ref-CSS2">CSS2</a>], section 4.1.3).</p>
<p>Because presentation attributes are expressed as XML
-attributes, presentation attributes are case-sensitive and must
-match the exact name as specified in the <a href='svgdtd.html'>DTD</a>
-(see the <code>SVG.Presentation.attrib</code> entity in the DTD,
-which expands to all of the presentation attributes).
+attributes, their names are case-sensitive and must be
+given exactly as they are defined.
When using a presentation attribute to specify a value for the
<a>'fill'</a> property, the presentation attribute must be
be specified as <span class='attr-value'>fill="…"</span> and not