<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="../../../tools/errata/errata2xhtml.xsl"?>

<!--
  Entity declaration for &nbsp; in HTML. xsltproc does not recognise this
  unless it's declared.
-->
<!DOCTYPE errata [
  <!ENTITY nbsp " ">
  <!ENTITY eacute "é">
]>

<errata xmlns="http://www.w3.org/2005/04/svg-errata" xmlns:h="http://www.w3.org/1999/xhtml">
  <!--
    - statuses:
            draft - the erratum is a work in progress
            proposed - the working group considers the erratum to be ready for Call for Review of Proposed Corrections
                       http://www.w3.org/2005/10/Process-20051014/tr.html#cfr-corrections
            normative - the erratum has passed the criteria set out in Modifying a W3C Recommendation
                        http://www.w3.org/2005/10/Process-20051014/tr.html#rec-modify
                        and is now normative and of equal status as the text in the published Recommendation
    - specs:
            t12 Tiny 1.2
            f12 Full 1.2
            f11 Full 1.1
            m11 Mobile 1.1
    - errata format is described in:
    http://www.w3.org/2005/10/Process-20051014/tr.html#errata
    Type 1 - No changes to text content
             These changes include fixing broken links or invalid markup.
    Type 2 - Corrections that do not affect conformance
             Editorial changes or clarifications that do not change the technical content of the specification.
    Type 3 - Corrections that MAY affect conformance, but add no new features
             These changes MAY affect conformance to the Recommendation. A change that affects conformance is one that:
             1. turns conforming data, processors, or other conforming agents into non-conforming agents, or
             2. turns non-conforming agents into conforming ones, or
             3. clears up an ambiguity or under-specified part of the specification in such a way that an agent whose conformance was once unclear becomes clearly conforming or non-conforming.
    Type 4 - New features
             DON'T DO THIS ONE BECAUSE IT'S NAUGHTY.
    -->

  <!--
  
  TEMPLATE FOR ERRATA
  
  Use 'discussion' for internal working group discussion, and 'comment' for public list discussion.
  
  For each change to the standard, create a change element.  Put the existing text in the current element, and the 
  
  <erratum status="draft | proposed | normative" spec="f11 | f12 | m11 | t12" cat="1 | 2 | 3 | 4 | ?" xml:id="">
    <title></title>
    <reporter email="">reporterName</reporter>
    <test-case href=""/>
    <pointer href=""/>
    <discussion href="" author=""/>
    <comment href=""/>
    <action href="" author="ACTION-XXXX OPEN | CLOSED authorName"/>
    <desc>
    </desc>
    <resolution>
    </resolution>
    <change href="">
        <current>
        </current>
        <replacement>
        </replacement>
    </change>
  </erratum>
  
  -->


  <!--
  <erratum status='draft' spec='f11' cat='' xml:id=''>
    <title></title>
    <reporter email=""></reporter>
    <discussion href="http://lists.w3.org/Archives/Public/www-svg/" author="foo"/>
    <action href="http://www.w3.org/Graphics/SVG/WG/track/actions/" author="ACTION- OPEN bar"/>
    <pointer href=""/>
    <comment href=""/>
    <discussion href=""/>
    <desc>
    </desc>
    <resolution>
    </resolution>
    <change href=''>
      <current>
        <p xmlns='http://www.w3.org/1999/xhtml'>
        </p>
      </current>
      <replacement>
        <p xmlns='http://www.w3.org/1999/xhtml'>
        </p>
      </replacement>
    </change>
  </erratum>
    -->

  <!--
    - search www-svg (notably jwatt)
    - search w3c-svg (notably something recent in minutes)
    - raxor has one
    - bjoern has a zillion
    - jwatt issues (related: http://www.w3.org/mid/40F66ECF.7080301%40croczilla.com)
    - http://lists.w3.org/Archives/Public/www-svg/2004Aug/0028.html
    - Jim's issues
    -->


  <!--
  <erratum status='draft' spec='f11' xml:id='events-feature'>
    <title>Feature strings SVGZoomEvents and SVGEvents not listed</title>
    <reporter email='jonathan.watt@strath.ac.uk'>Jonathan Watt</reporter>
    <pointer href='http://www.w3.org/TR/2003/REC-SVG11-20030114/svgdom.html#FeatureStrings'/>
    <test-case href='zoomevent-context.svg'/>
    <desc>
      The spec mentions screenX, screenY, clientX, clientY, altKey, ctrlKey,
      shiftKey, metaKey, relatedNode in relationship to this event when in reality
      they are only known to apply to MouseEvents or MutationEvents.
    </desc>
    <resolution>
      Just remove the additional fields from the context discussion.
    </resolution>
  </erratum>

    jwatt 'The feature string for this event set is "SVGEvents"'
    jwatt and
    jwatt 'The feature string for this event set is "SVGZoomEvents"'
    jwatt those aren't in the feature string list
    http://www.w3.org/TR/2003/REC-SVG11-20030114/feature.html
    darobin aren't those DOM features?
    http://www.w3.org/TR/2003/REC-SVG11-20030114/svgdom.html#FeatureStrings
    -->

  <!--
     ACTION #2005-176: Jon Erratum for events::EventTarget on SVGDocument for SVG 1.1
      http://lists.w3.org/Archives/Member/w3c-svg-wg/2005JanMar/1220.html
     ACTION #2005-146: Chris Create erratum per Alex's recommendation per ISSUE #2003-064
      http://lists.w3.org/Archives/Member/w3c-svg-wg/2005JanMar/att-0544/11-svg-irc.html
     ACTION #2005-143: Chris add erratum to remove foreignObject from list of elements that establish viewports.
      http://lists.w3.org/Archives/Member/w3c-svg-wg/2005JanMar/att-0544/11-svg-irc.html
     ACTION #2005-151: Chris Incorporate Peter's proposal on ISSUE #2003-004
      http://lists.w3.org/Archives/Member/w3c-svg-wg/2005JanMar/att-0544/11-svg-irc.html
     ACTION #2005-148: Dean Add Chris's writeup from 2004OctDec/0057.html to erratum
      http://lists.w3.org/Archives/Member/w3c-svg-wg/2005JanMar/att-0544/11-svg-irc.html
    -->

</errata>
