+ some actions completed; relative paths for images;
authorbjoern
Tue, 28 Mar 2006 00:09:58 +0900
changeset 13 a4c7b2939963
parent 12 606a0bb8873d
child 14 b2cd2e12c3e4
+ some actions completed; relative paths for images;
html/DOM3-Events.html
source/xml-source.xml
--- a/html/DOM3-Events.html	Mon Mar 27 20:47:14 2006 +0900
+++ b/html/DOM3-Events.html	Tue Mar 28 00:09:58 2006 +0900
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <!--
- Generated: Sun Mar 26 04:05:45 CEST 2006 hive
+ Generated: Mon Mar 27 17:08:07 CEST 2006 hive
  -->
 <html lang='en-US' xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US">
 <head>
@@ -281,10 +281,10 @@
 </li>
 <li class='tocline3'><a class='tocxref' href='#events-Events-interface'>1.7 Basic interfaces</a>
 <ul class='toc'>
-<li class='tocline4'><a href='#events-Events-Event'>Event</a>, <a href='#events-Events-EventTarget'>EventTarget</a>, <a href='#events-Events-EventListener'>EventListener</a>, <a href='#events-Events-EventException'>EventException</a>, <a href='#events-Events-EventException-EventExceptionCode'>EventExceptionCode</a></li>
+<li class='tocline4'><a href='#events-Events-Event'>Event</a>, <a href='#events-Events-CustomEvent'>CustomEvent</a>, <a href='#events-Events-EventTarget'>EventTarget</a>, <a href='#events-Events-EventListener'>EventListener</a>, <a href='#events-Events-EventException'>EventException</a>, <a href='#events-Events-EventException-EventExceptionCode'>EventExceptionCode</a></li>
 <li class='tocline4'><a class='tocxref' href='#events-Events-document'>1.7.1 Event creation</a>
 <ul>
-<li class='tocline5'><a href='#events-Events-DocumentEvent'>DocumentEvent</a>, <a href='#events-Events-CustomEvent'>CustomEvent</a></li>
+<li class='tocline5'><a href='#events-Events-DocumentEvent'>DocumentEvent</a></li>
 </ul>
 </li>
 </ul>
@@ -341,6 +341,7 @@
 <p><b>Note:</b> An implementation which does not conform to an event module can still implement the DOM interfaces associated with it. The DOM application can then create an event object using the <a href='#events-Events-DocumentEvent-createEvent'><code>DocumentEvent.createEvent()</code></a> method and dispatch an event type associated with this interface using the <a href='#events-Events-EventTarget-dispatchEvent'><code>EventTarget.dispatchEvent()</code></a> method.</p>
 <p>A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"Events"</code> and <code>"3.0"</code> (respectively) to determine whether or not DOM Level 3 Events is supported by the implementation. In order to fully support DOM Level 3 Events, an implementation must also support the "Core" feature defined in the DOM Level 2 Core specification [<cite><a class='noxref normative' href='#references-DOM2Core'>DOM Level 2 Core</a></cite>] and use the <a href='#events-Events-flow'>DOM event flow</a>. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref normative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. DOM Level 3 Events is built on top of DOM Level 2 Events [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>], i.e. a DOM Level 3 Events implementation where <code>hasFeature("Events", "3.0")</code> returns <code>true</code> must also return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>, <code>""</code> or, <code>null</code>.</p>
 <p>Each event module describes its own feature string in the event module listing.</p>
+<p><b>Note:</b> This specification is to be understood in the context of the DOM Level 3 Core specification [<cite><a class='noxref normative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>] and the general considerations for DOM implementations apply. For example, handling of <a href='#glossary-dt-namespaceURI'>namespace URIs</a> is discussed in <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations'><em>XML Namespaces</em></a>, and behavior in exceptional circumstances (such as when a <code>null</code> argument is passed when <code>null</code> was not expected) is discussed under <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187'><em>DOMException</em></a>.</p>
 </div>
 <!-- div3 Conformance --></div>
 <!-- div2 Events-overview -->
@@ -355,10 +356,10 @@
 <li>The <a href='#glossary-dt-target-phase'>target phase</a>: the event is dispatched to the <a href='#glossary-dt-target-node'>target node</a>.</li>
 <li>The <a href='#glossary-dt-bubbling-phase'>bubbling phase</a>: the event is dispatched to the target's ancestors from the direct parent of the <a href='#glossary-dt-target-node'>target node</a> to the root of the tree.</li>
 </ol>
-<div class='figure' style='text-align: center'><img src='http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/images/eventflow.png' alt='graphical representation of an event dispatched in a DOM tree using the DOM event flow' title='graphical representation of an event dispatched in a DOM tree using the DOM event flow' />
-<p style='text-align:left'><i>Figure: graphical representation of an event dispatched in a DOM tree using the DOM event flow</i> [<a href='http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/images/eventflow'>SVG 1.0 version</a>]</p>
-</div>
-<p><b>Note:</b> An <a class='normative' href='http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/images/eventflow.svg'>SVG 1.0 version of the representation above</a> is also available.</p>
+<div class='figure' style='text-align: center'><img src='images/eventflow.png' alt='graphical representation of an event dispatched in a DOM tree using the DOM event flow' title='graphical representation of an event dispatched in a DOM tree using the DOM event flow' />
+<p style='text-align:left'><i>Figure: graphical representation of an event dispatched in a DOM tree using the DOM event flow</i> [<a href='images/eventflow'>SVG 1.0 version</a>]</p>
+</div>
+<p><b>Note:</b> An <a class='normative' href='images/eventflow.svg'>SVG 1.0 version of the representation above</a> is also available.</p>
 <p>The target's ancestors are determined before the initial dispatch of the event. If the target node is removed during the dispatching, or a target's ancestor is added or removed, the event propagation will always be based on the target node and the target's ancestors determined before the dispatch.</p>
 <p>Some events may not necessarily accomplish the three phases of the DOM event flow, e.g. the event could only be defined for one or two phases. As an example, events defined in this specification will always accomplish the capture and target phases but some will not accomplish the bubbling phase ("bubbling events" versus "non-bubbling events", see also the <a href='#events-Events-Event-canBubble'><code>Event.bubbles</code></a> attribute).</p>
 </div>
@@ -427,9 +428,8 @@
 <p>The default actions are not part of the DOM Event flow. Before invoking a default action, the implementation must first dispatch the event as described in the <a href='#events-Events-flow'>DOM event flow</a>.</p>
 <p><a name='events-dt-cancelable-event' id="events-dt-cancelable-event"></a> A <i>cancelable event</i> is an event associated with a default action which is allowed to be canceled during the DOM event flow. At any phase during the event flow, the triggered event listeners have the option of canceling the default action or allowing the default action to proceed. In the case of the hyperlink in the browser, canceling the action would have the result of not activating the hyperlink. Not all events defined in this specification are cancelable events. See also <a href='#keyset-cancelable_keys'>Default actions and cancelable keyboard events</a>.</p>
 <p>Different implementations will specify their own default actions, if any, associated with each event. The DOM Events specification does not attempt to specify these actions.</p>
-<div style='color: red'>(<i><b>ED:</b></i> This is not entirely true, there are default actions for device event types when the events trigger activation, and there is a discussion about canceling keyboard events... )</div>
 <p>This specification does not provide mechanisms for accessing default actions or adding new ones.</p>
-<p>Implementations could react to an event before dispatching it and do changes on the display and the DOM tree. In such case, if a DOM attribute is changed before the event is fired, cancelling the device event type will also reverse the change. A good example is the attribute <code>HTMLInputElement.checked</code>: As described in [<cite><a class='noxref normative' href='#references-DOM2HTML'>DOM Level 2 HTML</a></cite>], the value of this property may be changed before the dispatch of the event; the user clicks on the radio button, the radio button is being checked (or unchecked) on the display, the attribute <code>HTMLInputElement.checked</code> is changed as well, and then the device event type <a href='#events-event-click'>click</a> is being dispatched. If the default action of the device event type is prevented, or if the default action attached to the <a href='#events-event-DOMActivate'>DOMActivate</a> event type is prevented, the property <code>HTMLInputElement.checked</code> will need to be changed back to its original value.</p>
+<p>Implementations could react to an event before dispatching it and do changes on the display and the DOM tree. In such case, if a DOM attribute is changed before the event is fired, cancelling the device event type will also reverse the change. A good example is the attribute <code>HTMLInputElement.checked</code>: As described in [<cite><a class='noxref informative' href='#references-DOM2HTML'>DOM Level 2 HTML</a></cite>], the value of this property may be changed before the dispatch of the event; the user clicks on the radio button, the radio button is being checked (or unchecked) on the display, the attribute <code>HTMLInputElement.checked</code> is changed as well, and then the device event type <a href='#events-event-click'>click</a> is being dispatched. If the default action of the device event type is prevented, or if the default action attached to the <a href='#events-event-DOMActivate'>DOMActivate</a> event type is prevented, the property <code>HTMLInputElement.checked</code> will need to be changed back to its original value.</p>
 </div>
 <!-- div2 Events-flow-cancelation -->
 <div class='div2'><a name='events-Events-flow-activation' id="events-Events-flow-activation"></a>
@@ -447,7 +447,7 @@
 <p>Each event is associated with a type, called <i>event type</i>. The event type is composed of a <a href='#glossary-dt-localname'>local name</a> and a <a href='#glossary-dt-namespaceURI'>namespace URI</a> as used in [<cite><a class='noxref normative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. All events defined in this specification are in no namespace.</p>
 <div class='div3'><a name='events-Events-EventTypes-category' id="events-Events-EventTypes-category"></a>
 <h3 id='events-Events-EventTypes-category-h3' class='div3'>1.5.1 Event types and event categories</h3>
-<p>An event type could be part of one or more categories. A category is represented using a <a href='#glossary-dt-localname'>local name</a> and a <a href='#glossary-dt-namespaceURI'>namespace URI</a> as defined in [<cite><a class='noxref normative' href='#references-Namespaces'>XML Namespaces</a></cite>]. The event types defined in this specification are not associated with one or more event categories and this specification does not provide methods to associate them. Other specifications may create and associate event categories with event listeners but in such case would need to inform the dispatch mechanism of those event categories. An example of the use of categories is given at <a href='#events-Events-registration-voicexmlevents'>Using VoiceXML Events</a>.</p>
+<p>An event type could be part of one or more categories. A category is represented using a <a href='#glossary-dt-localname'>local name</a> and a <a href='#glossary-dt-namespaceURI'>namespace URI</a> as defined in [<cite><a class='noxref normative' href='#references-Namespaces11'>XML Namespaces 1.1</a></cite>]. The event types defined in this specification are not associated with one or more event categories and this specification does not provide methods to associate them. Other specifications may create and associate event categories with event listeners but in such case would need to inform the dispatch mechanism of those event categories. An example of the use of categories is given at <a href='#events-Events-registration-voicexmlevents'>Using VoiceXML Events</a>.</p>
 </div>
 <!-- div3 Events-EventTypes-category -->
 <div class='div3'><a name='events-Events-EventTypes-complete' id="events-Events-EventTypes-complete"></a>
@@ -465,7 +465,7 @@
 <h3 id='events-Events-dom2-compatibility-h3' class='div3'>1.5.3 Compatibility with DOM Level 2 Events</h3>
 <p><a href='#glossary-dt-namespaceURI'>Namespace URIs</a> were only introduced in DOM Level 3 Events and were not part of DOM Level 2 Events.</p>
 <div style='color: red'>(<i><b>ED:</b></i> This, like all other relevant sections, does not yet reflect the changes to namespaced events the group agreed to. )</div>
-<p>Finally, DOM Level 3 Events considers that the <a href='#events-Events-Event-type'><code>Event.type</code></a> attribute is case sensitive, while DOM Level 2 Events considers <a class='noxref' href='#events-Events-Event-type'><code>Event.type</code></a> to be case insensitive.</p>
+<p>Finally, DOM Level 3 Events considers that the <a href='#events-Events-Event-type'><code>Event.type</code></a> attribute is case-sensitive, while DOM Level 2 Events considers <a class='noxref' href='#events-Events-Event-type'><code>Event.type</code></a> to be case-insensitive.</p>
 </div>
 <!-- div3 Events-dom2-compatibility --></div>
 <!-- div2 Event-types -->
@@ -709,6 +709,65 @@
 </dd>
 </dl>
 </dd>
+<dt><b>Interface <i><a name='events-Events-CustomEvent' id="events-Events-CustomEvent">CustomEvent</a></i></b> (introduced in <b class='since'>DOM Level 3</b>)</dt>
+<dd>
+<p>The CustomEvent interface is the recommended interface for application-specific event types. Unlike the Event interface it allows applications to provide contextual information about the event type.</p>
+<p>To create an instance of the <code>CustomEvent</code> interface, use the <a href='#events-Events-DocumentEvent-createEvent'><code>DocumentEvent.createEvent("CustomEvent")</code></a> method call.</p>
+<dl>
+<dt><br />
+<b>IDL Definition</b></dt>
+<dd>
+<div class='idl-code'>
+<pre>
+// Introduced in DOM Level 3:
+interface <a class='noxref' href='#events-Events-CustomEvent'>CustomEvent</a> : <a class='noxref' href='#events-Events-Event'>Event</a> {
+  readonly attribute DOMObject       <a class='noxref' href='#events-Events-CustomEvent-detail'>detail</a>;
+  void               <a class='noxref' href='#events-Events-Event-initCustomEventNS'>initCustomEventNS</a>(in DOMString namespaceURI, 
+                                       in DOMString typeArg, 
+                                       in boolean canBubbleArg, 
+                                       in boolean cancelableArg, 
+                                       in DOMObject detailArg);
+};
+</pre></div>
+<br /></dd>
+<dt><b>Attributes</b></dt>
+<dd>
+<dl>
+<dt><code class='attribute-name'><a name='events-Events-CustomEvent-detail' id="events-Events-CustomEvent-detail">detail</a></code> of type <code>DOMObject</code>, readonly</dt>
+<dd>Specifies some detail information about the <a href='#events-Events-Event'><code>Event</code></a>.<br /></dd>
+</dl>
+</dd>
+<dt><b>Methods</b></dt>
+<dd>
+<dl>
+<dt><code class='method-name'><a name='events-Events-Event-initCustomEventNS' id="events-Events-Event-initCustomEventNS">initCustomEventNS</a></code></dt>
+<dd>
+<div class='method'>The <code>initCustomEventNS</code> method is used to initialize the value of a <code>CustomEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
+<div class='parameters'><b>Parameters</b>
+<div class='paramtable'>
+<dl>
+<dt><code class='parameter-name'>namespaceURI</code> of type <code>DOMString</code></dt>
+<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class='parameter-name'>typeArg</code> of type <code>DOMString</code></dt>
+<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class='parameter-name'>canBubbleArg</code> of type <code>boolean</code></dt>
+<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class='parameter-name'>cancelableArg</code> of type <code>boolean</code></dt>
+<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
+<dt><code class='parameter-name'>detailArg</code> of type <code>DOMObject</code></dt>
+<dd>Specifies <a href='#events-Events-CustomEvent-detail'><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.<br /></dd>
+</dl>
+</div>
+</div>
+<!-- parameters -->
+<div><b>No Return Value</b></div>
+<div><b>No Exceptions</b></div>
+</div>
+<!-- method --></dd>
+</dl>
+</dd>
+</dl>
+</dd>
 <dt><b>Interface <i><a name='events-Events-EventTarget' id="events-Events-EventTarget">EventTarget</a></i></b> (introduced in <b class='since'>DOM Level 2</b>)</dt>
 <dd>
 <p>The <code>EventTarget</code> interface is implemented by all the objects which could be <a href='#glossary-dt-event-target'>event targets</a> in an implementation which supports the <a href='#events-Events-flows'>Event flows</a>. The interface allows registration and removal of event listeners, and dispatch of events to an event target.</p>
@@ -1081,64 +1140,6 @@
 </dd>
 </dl>
 </dd>
-<dt><b>Interface <i><a name='events-Events-CustomEvent' id="events-Events-CustomEvent">CustomEvent</a></i></b> (introduced in <b class='since'>DOM Level 3</b>)</dt>
-<dd>
-<p>@@@</p>
-<dl>
-<dt><br />
-<b>IDL Definition</b></dt>
-<dd>
-<div class='idl-code'>
-<pre>
-// Introduced in DOM Level 3:
-interface <a class='noxref' href='#events-Events-CustomEvent'>CustomEvent</a> : <a class='noxref' href='#events-Events-Event'>Event</a> {
-  readonly attribute DOMObject       <a class='noxref' href='#events-Events-CustomEvent-detail'>detail</a>;
-  void               <a class='noxref' href='#events-Events-Event-initCustomEventNS'>initCustomEventNS</a>(in DOMString namespaceURI, 
-                                       in DOMString typeArg, 
-                                       in boolean canBubbleArg, 
-                                       in boolean cancelableArg, 
-                                       in DOMObject detailArg);
-};
-</pre></div>
-<br /></dd>
-<dt><b>Attributes</b></dt>
-<dd>
-<dl>
-<dt><code class='attribute-name'><a name='events-Events-CustomEvent-detail' id="events-Events-CustomEvent-detail">detail</a></code> of type <code>DOMObject</code>, readonly</dt>
-<dd>Specifies some detail information about the <a href='#events-Events-Event'><code>Event</code></a>.<br /></dd>
-</dl>
-</dd>
-<dt><b>Methods</b></dt>
-<dd>
-<dl>
-<dt><code class='method-name'><a name='events-Events-Event-initCustomEventNS' id="events-Events-Event-initCustomEventNS">initCustomEventNS</a></code></dt>
-<dd>
-<div class='method'>The <code>initCustomEventNS</code> method is used to initialize the value of a <code>CustomEvent</code> object and has the same behavior as <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a>.
-<div class='parameters'><b>Parameters</b>
-<div class='paramtable'>
-<dl>
-<dt><code class='parameter-name'>namespaceURI</code> of type <code>DOMString</code></dt>
-<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
-<dt><code class='parameter-name'>typeArg</code> of type <code>DOMString</code></dt>
-<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
-<dt><code class='parameter-name'>canBubbleArg</code> of type <code>boolean</code></dt>
-<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
-<dt><code class='parameter-name'>cancelableArg</code> of type <code>boolean</code></dt>
-<dd>Refer to the <a href='#events-Events-Event-initEventNS'><code>Event.initEventNS()</code></a> method for a description of this parameter.<br /></dd>
-<dt><code class='parameter-name'>detailArg</code> of type <code>DOMObject</code></dt>
-<dd>Specifies <a href='#events-Events-CustomEvent-detail'><code>CustomEvent.detail</code></a>. This value may be <code>null</code>.<br /></dd>
-</dl>
-</div>
-</div>
-<!-- parameters -->
-<div><b>No Return Value</b></div>
-<div><b>No Exceptions</b></div>
-</div>
-<!-- method --></dd>
-</dl>
-</dd>
-</dl>
-</dd>
 </dl>
 </div>
 <!-- div3 Events-document --></div>
@@ -1246,7 +1247,7 @@
 </dl>
 </dd>
 </dl>
-<p>The User Interface event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"UIEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the DOM Level 3 User Interface event types are supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification and the <code>"Views"</code> feature defined in the DOM Level 2 Views specification [<cite><a class='noxref normative' href='#references-DOM2Views'>DOM Level 2 Views</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>].</p>
+<p>The User Interface event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"UIEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the DOM Level 3 User Interface event module are supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification and the <code>"Views"</code> feature defined in the DOM Level 2 Views specification [<cite><a class='noxref normative' href='#references-DOM2Views'>DOM Level 2 Views</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>].</p>
 <p><b>Note:</b> The DOM Level 3 User Interface Events module does not include the event types <code>DOMFocusIn</code> and <code>DOMFocusOut</code> defined in [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>]. This implies that a DOM Level 3 User Interface Events implementation where <code>hasFeature("UIEvents", "3.0")</code> returns <code>true</code> does not necessarily return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>.</p>
 <div class='event-definition'>
 <dl>
@@ -1396,7 +1397,7 @@
 <dd>
 <dl>
 <dt><code class='attribute-name'><a name='events-Events-UIEvent-data' id="events-Events-UIEvent-data">data</a></code> of type <code>DOMString</code>, readonly</dt>
-<dd><code>data</code> holds the value of the characters generated by the character device. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class='noxref normative' href='#references-Unicode'>Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <i>NFC</i>, defined in [<cite><a class='noxref normative' href='#references-UnicodeNormalization'>UTR #15</a></cite>]. This attribute cannot be null or contain the empty string.<br /></dd>
+<dd><code>data</code> holds the value of the characters generated by the character device. This may be a single Unicode character or a non-empty sequence of Unicode characters [<cite><a class='noxref normative' href='#references-Unicode'>Unicode</a></cite>]. Characters should be normalized as defined by the Unicode normalization form <i>NFC</i>, defined in [<cite><a class='noxref normative' href='#references-UnicodeNormalization'>UAX #15</a></cite>]. This attribute cannot be null or contain the empty string.<br /></dd>
 </dl>
 </dd>
 <dt><b>Methods</b></dt>
@@ -2363,7 +2364,7 @@
 </dl>
 </dd>
 </dl>
-<p>The mutation event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"MutationEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the <a href='#events-Events-MutationEvent'><code>MutationEvent</code></a> is supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. This <a class='noxref' href='#events-Events-MutationEvent'><code>MutationEvent</code></a> interface is built on top of the DOM Level 2 Mutation Events [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>] module, i.e. a DOM Level 3 <a class='noxref' href='#events-Events-MutationEvent'><code>MutationEvent</code></a> interface implementation where <code>hasFeature("MutationEvents","3.0")</code> returns <code>true</code> must also return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>, <code>""</code> or, <code>null</code>.</p>
+<p>The mutation event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values <code>"MutationEvents"</code> and <code>"3.0"</code> (respectively) to determine whether or not the Mutation event module is supported by the implementation. In order to fully support this module, an implementation must also support the <code>"Events"</code> feature defined in this specification. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. This <a href='#events-Events-MutationEvent'><code>MutationEvent</code></a> interface is built on top of the DOM Level 2 Mutation Events [<cite><a class='noxref normative' href='#references-DOM2Events'>DOM Level 2 Events</a></cite>] module, i.e. a DOM Level 3 <a class='noxref' href='#events-Events-MutationEvent'><code>MutationEvent</code></a> interface implementation where <code>hasFeature("MutationEvents","3.0")</code> returns <code>true</code> must also return <code>true</code> when the <code>version</code> number is <code>"2.0"</code>, <code>""</code> or, <code>null</code>.</p>
 <div class='event-definition'>
 <dl>
 <dt><a name='events-event-DOMSubtreeModified' id="events-event-DOMSubtreeModified"></a><a class='noxref' href='#events-event-DOMSubtreeModified'>DOMSubtreeModified</a></dt>
@@ -2398,7 +2399,7 @@
 <td valign='top' rowspan='1' colspan='1'>None</td>
 </tr>
 </table>
-This is a general event for notification of all changes to the document. It can be used instead of the more specific events listed below. It may be dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter use should generally be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event is the lowest common parent of the changes which have taken place. This event is dispatched after any other events caused by the mutation(s) have occurred.</dd>
+This is a general event for notification of all changes to the document. It can be used instead of the more specific mutation and mutation name events listed below. It may be dispatched after a single modification to the document or, at the implementation's discretion, after multiple changes have occurred. The latter use should generally be used to accommodate multiple changes which occur either simultaneously or in rapid succession. The target of this event is the lowest common parent of the changes which have taken place. This event is dispatched after any other events caused by the mutation(s) have occurred.</dd>
 </dl>
 </div>
 <div class='event-definition'>
@@ -2432,7 +2433,7 @@
 </tr>
 <tr>
 <th rowspan='1' colspan='1'>Context info</th>
-<td valign='top' rowspan='1' colspan='1'><a href='#events-Events-MutationEvent-relatedNode'><code>MutationEvent.relatedNode</code></a> holds the parent node of the node being inserted.</td>
+<td valign='top' rowspan='1' colspan='1'><a href='#events-Events-MutationEvent-relatedNode'><code>MutationEvent.relatedNode</code></a> holds the parent node of the node that has been inserted or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</td>
 </tr>
 </table>
 A node has been added as a <a href='#glossary-dt-child'>child</a> of another node or, in case of <code>Attr</code> nodes, has been added to an <code>Element</code>. This event is dispatched after the insertion has taken place. The <a href='#glossary-dt-target-node'>target node</a> of this event is the node being inserted.</dd>
@@ -2469,7 +2470,7 @@
 </tr>
 <tr>
 <th rowspan='1' colspan='1'>Context info</th>
-<td valign='top' rowspan='1' colspan='1'><a href='#events-Events-MutationEvent-relatedNode'><code>MutationEvent.relatedNode</code></a> holds the parent node of the node being removed.</td>
+<td valign='top' rowspan='1' colspan='1'><a href='#events-Events-MutationEvent-relatedNode'><code>MutationEvent.relatedNode</code></a> holds the parent node of the node being removed or, in case of <code>Attr</code> nodes, the <code>ownerElement</code> of the <code>Attr</code> node.</td>
 </tr>
 </table>
 A node is being removed from its parent node or, in case of <code>Attr</code> nodes, removed from its <code>ownerElement</code>. This event is dispatched before the removal takes place. The <a href='#glossary-dt-target-node'>target node</a> of this event is the node being removed.</dd>
@@ -2727,7 +2728,7 @@
 </dl>
 </dd>
 </dl>
-<p>The mutation name event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values "MutationNameEvents" and "3.0" (respectively) to determine whether or not the <a href='#events-Events-MutationNameEvent'><code>MutationNameEvent</code></a> is supported by the implementation. In order to fully support this module, an implementation must also support the <code>"MutationEvents"</code> feature defined in this specification and the <code>"Core"</code> feature defined in the DOM Level 3 Core specification [<cite><a class='noxref normative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>].</p>
+<p>The mutation name event types are listed below. A DOM application may use the <code>hasFeature(feature, version)</code> method of the <code>DOMImplementation</code> interface with parameter values "MutationNameEvents" and "3.0" (respectively) to determine whether or not the Mutation Name event module is supported by the implementation. In order to fully support this module, an implementation must also support the <code>"MutationEvents"</code> feature defined in this specification and the <code>"Core"</code> feature defined in the DOM Level 3 Core specification [<cite><a class='noxref normative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>]. For additional information about <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance'><em>conformance</em></a>, please see the DOM Level 3 Core specification [<cite><a class='noxref informative' href='#references-DOMCore'>DOM Level 3 Core</a></cite>].</p>
 <div class='event-definition'>
 <dl>
 <dt><a name='events-event-DOMElementNameChanged' id="events-event-DOMElementNameChanged"></a><a class='noxref' href='#events-event-DOMElementNameChanged'>DOMElementNameChanged</a></dt>
@@ -2955,9 +2956,7 @@
 <td valign='top' rowspan='1' colspan='1'><a href='#events-Events-UIEvent-view'><code>UIEvent.view</code></a> may be in use.</td>
 </tr>
 </table>
-The document, or a resource linked from it, has been loaded but cannot be interpreted according to its semantic, such as an invalid image, a script execution error, or non-well-formed XML.
-<div style='color: red'>(<i><b>ED:</b></i> See open issues <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/15'>ISSUE-15</a> and <a class='normative' href='http://lists.w3.org/Archives/Member/member-webapi/2006Feb/0039'>http://lists.w3.org/Archives/Member/member-webapi/2006Feb/0039</a>. )</div>
-</dd>
+A resource failed to load, or has been loaded but cannot be interpreted according to its semantics such as an invalid image, a script execution error, or non-well-formed XML.</dd>
 </dl>
 </div>
 <div class='event-definition'>
@@ -3769,7 +3768,7 @@
 <div class='div3'><a name='changes-DOMEvents2to3Changes-event-types' id="changes-DOMEvents2to3Changes-event-types"></a>
 <h3 id='changes-DOMEvents2to3Changes-event-types-h3' class='adiv3'>B.1.2 Changes to DOM Level 2 event types</h3>
 <p>Lots of clarifications have been made on the event types. The conformance is now explicitly defined against the event types, and not only in terms of interfaces required by the event types. Support for namespaces and the features <code>"BasicEvents"</code>, <code>"TextEvents"</code>, <code>"KeyboardEvents"</code>, and <code>"MutationNameEvents"</code> have been introduced.</p>
-<p>The DOM Level 2 Event <a href='#events-event-load'>load</a> event type can now be dispatched to more [<cite><a class='noxref normative' href='#references-HTML40'>HTML 4.01</a></cite>] elements. <a href='#events-event-blur'>blur</a> and <a href='#events-event-focus'>focus</a> have been clarified and restricted to [<cite><a class='noxref normative' href='#references-HTML40'>HTML 4.01</a></cite>] applications only.</p>
+<p>The DOM Level 2 Event <a href='#events-event-load'>load</a> event type can now be dispatched to more [<cite><a class='noxref informative' href='#references-HTML40'>HTML 4.01</a></cite>] elements. <a href='#events-event-blur'>blur</a> and <a href='#events-event-focus'>focus</a> have been clarified and restricted to [<cite><a class='noxref informative' href='#references-HTML40'>HTML 4.01</a></cite>] applications only.</p>
 </div>
 <!-- div3 DOMEvents2to3Changes-event-types -->
 <div class='div3'><a name='changes-DOMLevel2to3Changes' id="changes-DOMLevel2to3Changes"></a>
@@ -3873,6 +3872,16 @@
                                    in boolean cancelableArg);
   };
 
+  // Introduced in DOM Level 3:
+  interface <a class='noxref' href='#events-Events-CustomEvent'>CustomEvent</a> : <a class='noxref' href='#events-Events-Event'>Event</a> {
+    readonly attribute DOMObject       <a class='noxref' href='#events-Events-CustomEvent-detail'>detail</a>;
+    void               <a class='noxref' href='#events-Events-Event-initCustomEventNS'>initCustomEventNS</a>(in DOMString namespaceURI, 
+                                         in DOMString typeArg, 
+                                         in boolean canBubbleArg, 
+                                         in boolean cancelableArg, 
+                                         in DOMObject detailArg);
+  };
+
   // Introduced in DOM Level 2:
   interface <a class='noxref' href='#events-Events-EventTarget'>EventTarget</a> {
     void               <a class='noxref' href='#events-Events-EventTarget-addEventListener'>addEventListener</a>(in DOMString type, 
@@ -3912,16 +3921,6 @@
                                    in DOMString type);
   };
 
-  // Introduced in DOM Level 3:
-  interface <a class='noxref' href='#events-Events-CustomEvent'>CustomEvent</a> : <a class='noxref' href='#events-Events-Event'>Event</a> {
-    readonly attribute DOMObject       <a class='noxref' href='#events-Events-CustomEvent-detail'>detail</a>;
-    void               <a class='noxref' href='#events-Events-Event-initCustomEventNS'>initCustomEventNS</a>(in DOMString namespaceURI, 
-                                         in DOMString typeArg, 
-                                         in boolean canBubbleArg, 
-                                         in boolean cancelableArg, 
-                                         in DOMObject detailArg);
-  };
-
   // Introduced in DOM Level 2:
   interface <a class='noxref' href='#events-Events-UIEvent'>UIEvent</a> : <a class='noxref' href='#events-Events-Event'>Event</a> {
     readonly attribute views::AbstractView <a class='noxref' href='#events-Events-UIEvent-view'>view</a>;
@@ -4166,6 +4165,22 @@
 
 }
 </pre></div>
+<h3 id='java-binding-org.w3c.dom.events.CustomEvent'>org\w3c\dom\events\CustomEvent.java:</h3>
+<div class='java-code'>
+<pre>
+package org.w3c.dom.events;
+
+public interface CustomEvent extends Event {
+    public Object getDetail();
+
+    public void initCustomEventNS(String namespaceURI, 
+                                  String typeArg, 
+                                  boolean canBubbleArg, 
+                                  boolean cancelableArg, 
+                                  Object detailArg);
+
+}
+</pre></div>
 <h3 id='java-binding-org.w3c.dom.events.EventTarget'>org\w3c\dom\events\EventTarget.java:</h3>
 <div class='java-code'>
 <pre>
@@ -4224,22 +4239,6 @@
 
 }
 </pre></div>
-<h3 id='java-binding-org.w3c.dom.events.CustomEvent'>org\w3c\dom\events\CustomEvent.java:</h3>
-<div class='java-code'>
-<pre>
-package org.w3c.dom.events;
-
-public interface CustomEvent extends Event {
-    public Object getDetail();
-
-    public void initCustomEventNS(String namespaceURI, 
-                                  String typeArg, 
-                                  boolean canBubbleArg, 
-                                  boolean cancelableArg, 
-                                  Object detailArg);
-
-}
-</pre></div>
 <h3 id='java-binding-org.w3c.dom.events.UIEvent'>org\w3c\dom\events\UIEvent.java:</h3>
 <div class='java-code'>
 <pre>
@@ -4483,7 +4482,6 @@
 <div class='div1'><a name='ecma-script-binding-ecma-binding' id="ecma-script-binding-ecma-binding"></a>
 <h1 id='ecma-script-binding-ecma-binding-h1' class='adiv1'>Appendix E: ECMAScript Language Binding</h1>
 <p class='first'>This appendix contains the complete ECMAScript [<cite><a class='noxref normative' href='#references-ECMAScript'>ECMAScript</a></cite>] binding for the Level 3 Document Object Model Events definitions.</p>
-<div style='color: red'>(<i><b>ED:</b></i> There a some open issues regarding clarifications around terms such as 'read-only', <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/24'>ISSUE-24: DOM3EV: DontDelete and other internal properties</a>, <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/23'>ISSUE-23: DOM3EV: passing non-Strings to String methods</a>, <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/22'>ISSUE-22: DOM3EV: Define what "read-only" means for ECMAScript</a>, and see also <a class='normative' href='http://www.w3.org/mid/[email protected]'>Proposed rewrite of DOM3EV Appendix E</a>, <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/21'>ISSUE-21: Should we use RFC 2119 keywords keywords consistently to state conformance requirements?</a>; see also <a class='normative' href='http://www.w3.org/2005/06/tracker/webapi/issues/13'>ISSUE-13</a>. )</div>
 <div class='ecma-block'>
 <dl>
 <dt>Properties of the <b>Event</b> Constructor function:</dt>
@@ -4547,6 +4545,31 @@
 </dd>
 </dl>
 </dd>
+<dt>Objects that implement the <b>CustomEvent</b> interface:</dt>
+<dd>
+<dl>
+<dt>Objects that implement the <b>CustomEvent</b> interface have all properties and functions of the <b>Event</b> interface as well as the properties and functions defined below.</dt>
+<dt>Properties of objects that implement the <b>CustomEvent</b> interface:</dt>
+<dd>
+<dl>
+<dt><b>detail</b></dt>
+<dd>This read-only property is an object that implements the <b>Object</b> interface.</dd>
+</dl>
+</dd>
+<dt>Functions of objects that implement the <b>CustomEvent</b> interface:</dt>
+<dd>
+<dl>
+<dt><b>initCustomEventNS(namespaceURI, typeArg, canBubbleArg, cancelableArg, detailArg)</b></dt>
+<dd>This function has no return value.<br />
+The <b>namespaceURI</b> parameter is a <b>String</b>.<br />
+The <b>typeArg</b> parameter is a <b>String</b>.<br />
+The <b>canBubbleArg</b> parameter is a <b>Boolean</b>.<br />
+The <b>cancelableArg</b> parameter is a <b>Boolean</b>.<br />
+The <b>detailArg</b> parameter is an object that implements the <b>Object</b> interface.</dd>
+</dl>
+</dd>
+</dl>
+</dd>
 <dt>Objects that implement the <b>EventTarget</b> interface:</dt>
 <dd>
 <dl>
@@ -4625,31 +4648,6 @@
 </dd>
 </dl>
 </dd>
-<dt>Objects that implement the <b>CustomEvent</b> interface:</dt>
-<dd>
-<dl>
-<dt>Objects that implement the <b>CustomEvent</b> interface have all properties and functions of the <b>Event</b> interface as well as the properties and functions defined below.</dt>
-<dt>Properties of objects that implement the <b>CustomEvent</b> interface:</dt>
-<dd>
-<dl>
-<dt><b>detail</b></dt>
-<dd>This read-only property is an object that implements the <b>Object</b> interface.</dd>
-</dl>
-</dd>
-<dt>Functions of objects that implement the <b>CustomEvent</b> interface:</dt>
-<dd>
-<dl>
-<dt><b>initCustomEventNS(namespaceURI, typeArg, canBubbleArg, cancelableArg, detailArg)</b></dt>
-<dd>This function has no return value.<br />
-The <b>namespaceURI</b> parameter is a <b>String</b>.<br />
-The <b>typeArg</b> parameter is a <b>String</b>.<br />
-The <b>canBubbleArg</b> parameter is a <b>Boolean</b>.<br />
-The <b>cancelableArg</b> parameter is a <b>Boolean</b>.<br />
-The <b>detailArg</b> parameter is an object that implements the <b>Object</b> interface.</dd>
-</dl>
-</dd>
-</dl>
-</dd>
 <dt>Objects that implement the <b>UIEvent</b> interface:</dt>
 <dd>
 <dl>
@@ -4998,9 +4996,9 @@
 <dt><b><a name='glossary-dt-event-target' id="glossary-dt-event-target">event target</a></b></dt>
 <dd>The object to which an <a href='#glossary-dt-event'>event</a> is targeted.</dd>
 <dt><b><a name='glossary-dt-localname' id="glossary-dt-localname">local name</a></b></dt>
-<dd>See local name in Namespaces in XML 1.1 [<cite><a class='noxref informative' href='#references-Namespaces11'>XML Namespaces 1.1</a></cite>].</dd>
+<dd>See local name in [<cite><a class='noxref informative' href='#references-Namespaces11'>XML Namespaces 1.1</a></cite>].</dd>
 <dt><b><a name='glossary-dt-namespaceURI' id="glossary-dt-namespaceURI">namespace URI</a></b></dt>
-<dd>A <i>namespace URI</i> is a URI that identifies an XML namespace. This is called the namespace name in Namespaces in XML [<cite><a class='noxref informative' href='#references-Namespaces'>XML Namespaces</a></cite>]. See also sections 1.3.2 "<a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#baseURIs-Considerations'><em>DOM URIs</em></a>" and 1.3.3 "<a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations'><em>XML Namespaces</em></a>" regarding URIs and namespace URIs handling and comparison in the DOM APIs.</dd>
+<dd>A <i>namespace URI</i> is a URI that identifies an XML namespace. This is called the namespace name in [<cite><a class='noxref informative' href='#references-Namespaces11'>XML Namespaces 1.1</a></cite>]. See also sections 1.3.2 "<a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#baseURIs-Considerations'><em>DOM URIs</em></a>" and 1.3.3 "<a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations'><em>XML Namespaces</em></a>" regarding URIs and namespace URIs handling and comparison in the DOM APIs.</dd>
 <dt><b><a name='glossary-dt-target-node' id="glossary-dt-target-node">target node</a></b></dt>
 <dd>The target node is the node representing the <a href='#glossary-dt-event-target'>event target</a> to which an <a href='#glossary-dt-event'>event</a> is targeted using the DOM event flow.</dd>
 <dt><b><a name='glossary-dt-target-phase' id="glossary-dt-target-phase">target phase</a></b></dt>
@@ -5019,29 +5017,23 @@
 <h2 id='references-References-Normative-h2' class='adiv2'>H.1 Normative references</h2>
 <dl>
 <dt><b>[<a name='references-DOM2Core' id="references-DOM2Core">DOM Level 2 Core</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113'>Document Object Model Level 2 Core Specification</a></cite>, A. Le Hors, et al., Editors. World Wide Web Consortium, 13 November 2000. This version of the DOM Level 2 Core Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Core'>latest version of DOM Level 2 Core</a> is available at http://www.w3.org/TR/DOM-Level-2-Core.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113'>Document Object Model Level 2 Core Specification</a></cite>, A. Le Hors, et al., Editors. World Wide Web Consortium, November 2000. This version of the DOM Level 2 Core Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Core'>latest version of DOM Level 2 Core</a> is available at http://www.w3.org/TR/DOM-Level-2-Core.</dd>
 <dt><b>[<a name='references-DOMCore' id="references-DOMCore">DOM Level 3 Core</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/CR-DOM-Level-3-Core-20031107'>Document Object Model Level 3 Core Specification</a></cite>, A. Le Hors, et al., Editors. World Wide Web Consortium, November 2003. This version of the Document Object Model Level 3 Core Specification is http://www.w3.org/TR/2003/CR-DOM-Level-3-Core-20031107. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core'>latest version of DOM Level 3 Core</a> is available at http://www.w3.org/TR/DOM-Level-3-Core.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407'>Document Object Model Level 3 Core Specification</a></cite>, A. Le Hors, et al., Editors. World Wide Web Consortium, April 2004. This version of the Document Object Model Level 3 Core Specification is http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-Core'>latest version of DOM Level 3 Core</a> is available at http://www.w3.org/TR/DOM-Level-3-Core.</dd>
 <dt><b>[<a name='references-DOM2Events' id="references-DOM2Events">DOM Level 2 Events</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113'>Document Object Model Level 2 Events Specification</a></cite>, T. Pixley, Editor. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Events Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Events'>latest version of Document Object Model Level 2 Events</a> is available at http://www.w3.org/TR/DOM-Level-2-Events.</dd>
-<dt><b>[<a name='references-DOM2HTML' id="references-DOM2HTML">DOM Level 2 HTML</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109'>Document Object Model Level 2 HTML Specification</a></cite>, J. Stenback, et al., Editors. World Wide Web Consortium, 9 January 2003. This version of the Document Object Model Level 2 HTML Recommendation is http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-HTML'>latest version of Document Object Model Level 2 HTML</a> is available at http://www.w3.org/TR/DOM-Level-2-HTML.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113'>Document Object Model Level 2 Events Specification</a></cite>, T. Pixley, Editor. World Wide Web Consortium, November 2000. This version of the Document Object Model Level 2 Events Specification is http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Events'>latest version of Document Object Model Level 2 Events</a> is available at http://www.w3.org/TR/DOM-Level-2-Events.</dd>
 <dt><b>[<a name='references-DOM2Views' id="references-DOM2Views">DOM Level 2 Views</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113'>Document Object Model Level 2 Views Specification</a></cite>, A. Le Hors, L. Cable, Editors. World Wide Web Consortium, 13 November 2000. This version of the Document Object Model Level 2 Views Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Views'>latest version of Document Object Model Level 2 Views</a> is available at http://www.w3.org/TR/DOM-Level-2-Views.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113'>Document Object Model Level 2 Views Specification</a></cite>, A. Le Hors, L. Cable, Editors. World Wide Web Consortium, November 2000. This version of the Document Object Model Level 2 Views Recommendation is http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-Views'>latest version of Document Object Model Level 2 Views</a> is available at http://www.w3.org/TR/DOM-Level-2-Views.</dd>
 <dt><b>[<a name='references-ECMAScript' id="references-ECMAScript">ECMAScript</a>]</b></dt>
 <dd><cite>ECMAScript Language Specification</cite>, Third Edition. European Computer Manufacturers Association, Standard ECMA-262, December 1999. This version of the ECMAScript Language is available from http://www.ecma-international.org/.</dd>
-<dt><b>[<a name='references-HTML40' id="references-HTML40">HTML 4.01</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/1999/REC-html401-19991224/'>HTML 4.01 Specification</a></cite>, D. Raggett, A. Le Hors, and I. Jacobs, Editors. World Wide Web Consortium, 17 December 1997, revised 24 April 1998, revised 24 December 1999. This version of the HTML 4.01 Recommendation is http://www.w3.org/TR/1999/REC-html401-19991224. The <a class='normative' href='http://www.w3.org/TR/html4'>latest version of HTML 4</a> is available at http://www.w3.org/TR/html4.</dd>
 <dt><b>[<a name='references-Java' id="references-Java">Java</a>]</b></dt>
 <dd><cite><a href='http://java.sun.com/docs/books/jls'>The Java Language Specification</a></cite>, J. Gosling, B. Joy, and G. Steele, Authors. Addison-Wesley, September 1996. Available at http://java.sun.com/docs/books/jls</dd>
 <dt><b>[<a name='references-OMGIDL' id="references-OMGIDL">OMG IDL</a>]</b></dt>
 <dd><cite>"OMG IDL Syntax and Semantics"</cite> defined in <cite><a href='http://www.omg.org/technology/documents/formal/corba_2.htm'>The Common Object Request Broker: Architecture and Specification, version 2</a></cite>, Object Management Group. The latest version of CORBA version 2.0 is available at http://www.omg.org/technology/documents/formal/corba_2.htm.</dd>
 <dt><b>[<a name='references-Unicode' id="references-Unicode">Unicode</a>]</b></dt>
 <dd><cite>The Unicode Standard, Version 4</cite>, ISBN 0-321-18578-1, as updated from time to time by the publication of new versions. The Unicode Consortium, 2000. See also <a class='normative' href='http://www.unicode.org/unicode/standard/versions'>Versions of the Unicode Standard</a>, available at http://www.unicode.org/unicode/standard/versions, for latest version and additional information on versions of the standard and of the Unicode Character Database.</dd>
-<dt><b>[<a name='references-UnicodeNormalization' id="references-UnicodeNormalization">UTR #15</a>]</b></dt>
-<dd><cite><a href='http://www.unicode.org/unicode/reports/tr15/'>Unicode Normalization Forms</a></cite>, The Unicode Standard Annex #15. The Unicode Consortium, 2003. The latest version of this annex is available at http://www.unicode.org/unicode/reports/tr15/.</dd>
-<dt><b>[<a name='references-Namespaces' id="references-Namespaces">XML Namespaces</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/1999/REC-xml-names-19990114/'>Namespaces in XML</a></cite>, T. Bray, D. Hollander, and A. Layman, Editors. World Wide Web Consortium, 14 January 1999. This version of the Namespaces in XML Recommendation is http://www.w3.org/TR/1999/REC-xml-names-19990114. The <a class='normative' href='http://www.w3.org/TR/REC-xml-names/'>latest version of Namespaces in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
+<dt><b>[<a name='references-UnicodeNormalization' id="references-UnicodeNormalization">UAX #15</a>]</b></dt>
+<dd><cite><a href='http://www.unicode.org/unicode/reports/tr15/'>Unicode Normalization Forms</a></cite>, The Unicode Standard Annex #15. The Unicode Consortium, 2005. The latest version of this annex is available at http://www.unicode.org/unicode/reports/tr15/.</dd>
 <dt><b>[<a name='references-Namespaces11' id="references-Namespaces11">XML Namespaces 1.1</a>]</b></dt>
 <dd><cite><a href='http://www.w3.org/TR/2004/REC-xml-names11-20040204/'>Namespaces in XML 1.1</a></cite>, T. Bray, D. Hollander, A. Layman, and R. Tobin, Editors. World Wide Web Consortium, February 2004. This version of the Namespaces in XML 1.1 Specification is http://www.w3.org/TR/2004/REC-xml-names11-20040204/. The <a class='normative' href='http://www.w3.org/TR/xml-names11/'>latest version of Namespaces in XML 1.1</a> is available at http://www.w3.org/TR/xml-names11/.</dd>
 </dl>
@@ -5051,25 +5043,29 @@
 <h2 id='references-References-Informative-h2' class='adiv2'>H.2 Informative references</h2>
 <dl>
 <dt><b>[<a name='references-DOMLS' id="references-DOMLS">DOM Level 3 Load and Save</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/CR-DOM-Level-3-LS-20031107'>Document Object Model Level 3 Load and Save Specification</a></cite>, J. Stenback, A. Heninger, Editors. World Wide Web Consortium, November 2003. This version of the DOM Level 3 Load and Save Specification is http://www.w3.org/TR/2003/CR-DOM-Level-3-LS-20031107. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-LS'>latest version of DOM Level 3 Load and Save</a> is available at http://www.w3.org/TR/DOM-Level-3-LS.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407'>Document Object Model Level 3 Load and Save Specification</a></cite>, J. Stenback, A. Heninger, Editors. World Wide Web Consortium, April 2004. This version of the DOM Level 3 Load and Save Specification is http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-3-LS'>latest version of DOM Level 3 Load and Save</a> is available at http://www.w3.org/TR/DOM-Level-3-LS.</dd>
+<dt><b>[<a name='references-DOM2HTML' id="references-DOM2HTML">DOM Level 2 HTML</a>]</b></dt>
+<dd><cite><a href='http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109'>Document Object Model Level 2 HTML Specification</a></cite>, J. Stenback, et al., Editors. World Wide Web Consortium, January 2003. This version of the Document Object Model Level 2 HTML Recommendation is http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109. The <a class='normative' href='http://www.w3.org/TR/DOM-Level-2-HTML'>latest version of Document Object Model Level 2 HTML</a> is available at http://www.w3.org/TR/DOM-Level-2-HTML.</dd>
 <dt><b>[<a name='references-DWW95' id="references-DWW95">DWW95</a>]</b></dt>
 <dd><cite>Developing International Software for Windows 95 and Windows NT: A Handbook for International Software Design</cite>, N. Kano, Author. Microsoft Press, 1995. ISBN 1-55615-840-8.</dd>
+<dt><b>[<a name='references-HTML40' id="references-HTML40">HTML 4.01</a>]</b></dt>
+<dd><cite><a href='http://www.w3.org/TR/1999/REC-html401-19991224/'>HTML 4.01 Specification</a></cite>, D. Raggett, A. Le Hors, and I. Jacobs, Editors. World Wide Web Consortium, December 1999. This version of the HTML 4.01 Recommendation is http://www.w3.org/TR/1999/REC-html401-19991224. The <a class='normative' href='http://www.w3.org/TR/html4'>latest version of HTML 4</a> is available at http://www.w3.org/TR/html4.</dd>
 <dt><b>[<a name='references-KeyEvent' id="references-KeyEvent">KeyEvent for Java</a>]</b></dt>
-<dd><cite><a href='http://java.sun.com/j2se/1.4.1/docs/api/java/awt/event/KeyEvent.html'>Java 2 SDK, Standard Edition Documentation, Version 1.4.1, Class java.awt.events.KeyEvent</a></cite>. Sun Microsystems. Available at http://java.sun.com/j2se/1.4.1/docs/api/java/awt/event/KeyEvent.html.</dd>
+<dd><cite><a href='http://java.sun.com/j2se/1.4.2/docs/api/java/awt/event/KeyEvent.html'>Java 2 SDK, Standard Edition Documentation, Version 1.4.2, Class java.awt.events.KeyEvent</a></cite>. Sun Microsystems. Available at http://java.sun.com/j2se/1.4.2/docs/api/java/awt/event/KeyEvent.html.</dd>
 <dt><b>[<a name='references-Keys' id="references-Keys">Keys enumeration for .Net</a>]</b></dt>
 <dd><cite><a href='http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp'>.NET Framework Class Library, Keys Enumeration</a></cite>. Microsoft. Available at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp.</dd>
 <dt><b>[<a name='references-SVG1' id="references-SVG1">SVG 1.1</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/REC-SVG11-20030114/'>Scalable Vector Graphics (SVG) 1.1 Specification</a></cite>, J. Ferraiolo, &#34276;&#27810; &#28147; (FUJISAWA Jun), and D. Jackson, Editors. World Wide Web Consortium, 14 January 2003. This version of the SVG 1.1 Recommendation is http://www.w3.org/TR/2003/REC-SVG11-20030114/. The <a class='normative' href='http://www.w3.org/TR/SVG'>latest version of SVG 1.1</a> is available at http://www.w3.org/TR/SVG.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2003/REC-SVG11-20030114/'>Scalable Vector Graphics (SVG) 1.1 Specification</a></cite>, J. Ferraiolo, &#34276;&#27810; &#28147; (FUJISAWA Jun), and D. Jackson, Editors. World Wide Web Consortium, January 2003. This version of the SVG 1.1 Recommendation is http://www.w3.org/TR/2003/REC-SVG11-20030114/. The <a class='normative' href='http://www.w3.org/TR/SVG11/'>latest version of SVG 1.1</a> is available at http://www.w3.org/TR/SVG11/.</dd>
 <dt><b>[<a name='references-VoiceXML20' id="references-VoiceXML20">VoiceXML 2.0</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/CR-voicexml20-20030220'>Voice Extensible Markup Language (VoiceXML) Version 2.0</a></cite>, S. McGlashan, et al., Editors. World Wide Web Consortium, February 2003. This version of the Voice Extensible Markup Language Version 2.0 specification is http://www.w3.org/TR/2003/CR-voicexml20-20030220. The <a class='normative' href='http://www.w3.org/TR/voicexml20/'>latest version of Voice Extensible Markup Language Version 2.0</a> is available at http://www.w3.org/TR/voicexml20/.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2004/REC-voicexml20-20040316/'>Voice Extensible Markup Language (VoiceXML) Version 2.0</a></cite>, S. McGlashan, et al., Editors. World Wide Web Consortium, March 2004. This version of the Voice Extensible Markup Language Version 2.0 Recommendation is http://www.w3.org/TR/2004/REC-voicexml20-20040316/. The <a class='normative' href='http://www.w3.org/TR/voicexml20/'>latest version of Voice Extensible Markup Language Version 2.0</a> is available at http://www.w3.org/TR/voicexml20/.</dd>
 <dt><b>[<a name='references-XForms10' id="references-XForms10">XForms 1.0</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/PR-xforms-20030801/'>XForms 1.0</a></cite>, M. Dubinko, et al., Editors. World Wide Web Consortium, August 2003. This version of the XForms 1.0 specification is http://www.w3.org/TR/2003/PR-xforms-20030801/. The <a class='normative' href='http://www.w3.org/TR/xforms/'>latest version of XForms 1.0</a> is available at http://www.w3.org/TR/xforms/.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2006/REC-xforms-20060314/'>XForms 1.0 (Second Edition)</a></cite>, M. Dubinko, et al., Editors. World Wide Web Consortium, March 2006. This version of the XForms 1.0 Recommendation is http://www.w3.org/TR/2006/REC-xforms-20060314/. The <a class='normative' href='http://www.w3.org/TR/xforms/'>latest version of XForms 1.0</a> is available at http://www.w3.org/TR/xforms/.</dd>
 <dt><b>[<a name='references-XHTML10' id="references-XHTML10">XHTML 1.0</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2002/REC-xhtml1-20020801'>XHTML 1.0: The Extensible HyperText Markup Language</a></cite>, S. Pemberton, et al., Authors. World Wide Web Consortium, 26 January 2000, revised 1 August 2002. This version of the XHTML 1.0 Recommendation is http://www.w3.org/TR/2002/REC-xhtml1-20020801. The <a class='normative' href='http://www.w3.org/TR/xhtml1'>latest version of XHTML 1.0</a> is available at http://www.w3.org/TR/xhtml1.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2002/REC-xhtml1-20020801'>XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)</a></cite>, S. Pemberton, et al., Authors. World Wide Web Consortium, August 2002. This version of the XHTML 1.0 Recommendation is http://www.w3.org/TR/2002/REC-xhtml1-20020801. The <a class='normative' href='http://www.w3.org/TR/xhtml1'>latest version of XHTML 1.0</a> is available at http://www.w3.org/TR/xhtml1.</dd>
 <dt><b>[<a name='references-XML' id="references-XML">XML 1.0</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2000/REC-xml-20001006'>Extensible Markup Language (XML) 1.0 (Second Edition)</a></cite>, T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 10 February 1998, revised 6 October 2000. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006. The <a class='normative' href='http://www.w3.org/TR/REC-xml'>latest version of XML 1.0</a> is available at http://www.w3.org/TR/REC-xml.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2004/REC-xml-20040204'>Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T. Bray, J. Paoli, C. M. Sperberg-McQueen, et. al, Editors. World Wide Web Consortium, February 2004. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <a class='normative' href='http://www.w3.org/TR/REC-xml'>latest version of XML 1.0</a> is available at http://www.w3.org/TR/REC-xml.</dd>
 <dt><b>[<a name='references-XMLEvents' id="references-XMLEvents">XML Events</a>]</b></dt>
-<dd><cite><a href='http://www.w3.org/TR/2003/REC-xml-events-20031014'>XML Events</a></cite>, S. McCarron, S. Pemberton, and T.V. Raman, Editors. World Wide Web Consortium, October 2003. This version of the XML Events specification is http://www.w3.org/TR/2003/REC-xml-events-20031014. The <a class='normative' href='http://www.w3.org/TR/xml-events/'>latest version of XML Events</a> is available at http://www.w3.org/TR/xml-events.</dd>
+<dd><cite><a href='http://www.w3.org/TR/2003/REC-xml-events-20031014'>XML Events</a></cite>, S. McCarron, S. Pemberton, and T.V. Raman, Editors. World Wide Web Consortium, October 2003. This version of the XML Events Recommendation is http://www.w3.org/TR/2003/REC-xml-events-20031014. The <a class='normative' href='http://www.w3.org/TR/xml-events/'>latest version of XML Events</a> is available at http://www.w3.org/TR/xml-events.</dd>
 </dl>
 </div>
 <!-- div2 References-Informative --></div>
@@ -5307,7 +5303,7 @@
 <td>&#160;</td>
 </tr>
 <tr>
-<td width='30%'><a class='noxref' href='#events-Event-types'>namespace URI</a> <a class='index-inst' href='#events-Event-types'>1</a>, <a class='index-inst' href='#events-Events-EventTypes-category'>2</a>, <a class='index-inst' href='#events-Events-dom2-compatibility'>3</a>, <a class='index-inst' href='#events-Events-Event-namespaceURI'>4</a>, <a class='index-inst' href='#events-Events-Event-initEventNS'>5</a>, <a class='index-inst' href='#glossary-dt-namespaceURI'>6</a></td>
+<td width='30%'><a class='noxref' href='#events-Conformance'>namespace URI</a> <a class='index-inst' href='#events-Conformance'>1</a>, <a class='index-inst' href='#events-Event-types'>2</a>, <a class='index-inst' href='#events-Events-EventTypes-category'>3</a>, <a class='index-inst' href='#events-Events-dom2-compatibility'>4</a>, <a class='index-inst' href='#events-Events-Event-namespaceURI'>5</a>, <a class='index-inst' href='#events-Events-Event-initEventNS'>6</a>, <a class='index-inst' href='#glossary-dt-namespaceURI'>7</a></td>
 <td width='30%'><a class='noxref' href='#events-Events-Event-namespaceURI'>namespaceURI</a></td>
 <td width='30%'><a class='noxref' href='#events-Events-MutationEvent-newValue'>newValue</a></td>
 </tr>
@@ -5382,13 +5378,13 @@
 <td>&#160;</td>
 </tr>
 <tr>
+<td width='30%'><a class='noxref' href='#events-Events-UIEvent-data'>UAX #15</a> <a class='index-inst' href='#events-Events-UIEvent-data'>1</a>, <a class='index-inst' href='#references-UnicodeNormalization'>2</a></td>
 <td width='30%'><a class='noxref' href='#events-Events-UIEvent'>UIEvent</a></td>
 <td width='30%'><a class='noxref' href='#events-Events-UIEvent-data'>Unicode</a> <a class='index-inst' href='#events-Events-UIEvent-data'>1</a>, <a class='index-inst' href='#references-Unicode'>2</a></td>
+</tr>
+<tr>
 <td width='30%'><a class='noxref' href='#events-event-unload'>unload</a> <a class='index-inst' href='#events-event-unload'>1</a></td>
-</tr>
-<tr>
 <td width='30%'><a class='noxref' href='#events-UNSPECIFIED_EVENT_TYPE_ERR'>UNSPECIFIED_EVENT_TYPE_ERR</a></td>
-<td width='30%'><a class='noxref' href='#events-Events-UIEvent-data'>UTR #15</a> <a class='index-inst' href='#events-Events-UIEvent-data'>1</a>, <a class='index-inst' href='#references-UnicodeNormalization'>2</a></td>
 </tr>
 <tr>
 <td>&#160;</td>
@@ -5407,8 +5403,7 @@
 </tr>
 <tr>
 <td width='30%'><a class='noxref' href='#events-Events-registration'>XML Events</a> <a class='index-inst' href='#events-Events-registration'>1</a>, <a class='index-inst' href='#events-Events-registration-xmlevents'>2</a>, <a class='index-inst' href='#references-XMLEvents'>3</a></td>
-<td width='30%'><a class='noxref' href='#events-Events-EventTypes-category'>XML Namespaces</a> <a class='index-inst' href='#events-Events-EventTypes-category'>1</a>, <a class='index-inst' href='#glossary-dt-namespaceURI'>2</a>, <a class='index-inst' href='#references-Namespaces'>3</a></td>
-<td width='30%'><a class='noxref' href='#events-Events-Event-type'>XML Namespaces 1.1</a> <a class='index-inst' href='#events-Events-Event-type'>1</a>, <a class='index-inst' href='#events-Events-EventTarget-dispatchEvent'>2</a>, <a class='index-inst' href='#glossary-dt-localname'>3</a>, <a class='index-inst' href='#references-Namespaces11'>4</a></td>
+<td width='30%'><a class='noxref' href='#events-Events-EventTypes-category'>XML Namespaces 1.1</a> <a class='index-inst' href='#events-Events-EventTypes-category'>1</a>, <a class='index-inst' href='#events-Events-Event-type'>2</a>, <a class='index-inst' href='#events-Events-EventTarget-dispatchEvent'>3</a>, <a class='index-inst' href='#glossary-dt-localname'>4</a>, <a class='index-inst' href='#glossary-dt-namespaceURI'>5</a>, <a class='index-inst' href='#references-Namespaces11'>6</a></td>
 </tr>
 </table>
 </div>
--- a/source/xml-source.xml	Mon Mar 27 20:47:14 2006 +0900
+++ b/source/xml-source.xml	Tue Mar 28 00:09:58 2006 +0900
@@ -652,6 +652,21 @@
       Each event module describes its own feature string in the event
       module listing.
      </p>
+
+     <note>
+      <p>
+       This specification is to be understood in the context of the DOM
+       Level 3 Core specification <bibref ref="DOMCore"/> and the
+       general considerations for DOM implementations apply. For
+       example, handling of <termref def="dt-namespaceURI">namespace
+       URIs</termref> is discussed in
+       <xspecref href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Namespaces-Considerations">XML
+       Namespaces</xspecref>, and behavior in exceptional circumstances
+       (such as when a <code>null</code> argument is passed when
+       <code>null</code> was not expected) is discussed under
+       <xspecref href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187">DOMException</xspecref>.
+      </p>
+     </note>
     </div3>
    </div2>
 
@@ -714,13 +729,12 @@
       </item>
      </olist>
 <!-- @@@ refer to local versions -->
-     <graphic source="http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/images/eventflow.png" alt="graphical representation of an event dispatched in a DOM tree using the DOM event flow"/>
+     <graphic source="images/eventflow.png" alt="graphical representation of an event dispatched in a DOM tree using the DOM event flow"/>
 
      <note>
       <p>
-       An
-       <loc href="http://www.w3.org/TR/2003/NOTE-DOM-Level-3-Events-20031107/images/eventflow.svg">SVG
-       1.0 version of the representation above</loc> is also available.
+       An <loc href="images/eventflow.svg">SVG 1.0 version of the
+       representation above</loc> is also available.
       </p>
      </note>
 
@@ -1006,15 +1020,12 @@
      if any, associated with each event. The DOM Events specification
      does not attempt to specify these actions.
     </p>
-
-    <ednote>
-     <edtext>
+<!--
+      @@@
       This is not entirely true, there are default actions for device
       event types when the events trigger activation, and there is a
       discussion about canceling keyboard events...
-     </edtext>
-    </ednote>
-
+-->
     <p>
      This specification does not provide mechanisms for accessing
      default actions or adding new ones.
@@ -1224,9 +1235,9 @@
 
      <p>
       Finally, DOM Level 3 Events considers that the
-      <code>Event.type</code> attribute is case sensitive, while DOM
-      Level 2 Events considers <code>Event.type</code> to be case
-      insensitive.
+      <code>Event.type</code> attribute is case-sensitive, while DOM
+      Level 2 Events considers <code>Event.type</code> to be
+      case-insensitive.
      </p>
     </div3>
    </div2>
@@ -1849,6 +1860,100 @@
        </raises>
       </method>
      </interface>
+
+     <interface name="CustomEvent" inherits="Event" id="Events-CustomEvent" since="DOM Level 3">
+      <descr>
+       <p>
+        The CustomEvent interface is the recommended interface for
+        application-specific event types. Unlike the Event interface it
+        allows applications to provide contextual information about the
+        event type.
+       </p>
+
+       <p>
+        To create an instance of the <code>CustomEvent</code> interface,
+        use the <code>DocumentEvent.createEvent("CustomEvent")</code>
+        method call.
+       </p>
+      </descr>
+
+      <attribute id="Events-CustomEvent-detail" name="detail" type="DOMObject" readonly="yes">
+       <descr>
+        <p>
+         Specifies some detail information about the <code>Event</code>.
+        </p>
+       </descr>
+      </attribute>
+
+      <method name="initCustomEventNS" id="Events-Event-initCustomEventNS">
+       <descr>
+        <p>
+         The <code>initCustomEventNS</code> method is used to initialize
+         the value of a <code>CustomEvent</code> object and has the same
+         behavior as <code>Event.initEventNS()</code>.
+        </p>
+       </descr>
+
+       <parameters>
+        <param name="namespaceURI" type="DOMString" attr="in">
+         <descr>
+          <p>
+           Refer to the <code>Event.initEventNS()</code> method for a
+           description of this parameter.
+          </p>
+         </descr>
+        </param>
+
+        <param name="typeArg" type="DOMString" attr="in">
+         <descr>
+          <p>
+           Refer to the <code>Event.initEventNS()</code> method for a
+           description of this parameter.
+          </p>
+         </descr>
+        </param>
+
+        <param name="canBubbleArg" type="boolean" attr="in">
+         <descr>
+          <p>
+           Refer to the <code>Event.initEventNS()</code> method for a
+           description of this parameter.
+          </p>
+         </descr>
+        </param>
+
+        <param name="cancelableArg" type="boolean" attr="in">
+         <descr>
+          <p>
+           Refer to the <code>Event.initEventNS()</code> method for a
+           description of this parameter.
+          </p>
+         </descr>
+        </param>
+
+        <param name="detailArg" type="DOMObject" attr="in">
+         <descr>
+          <p>
+           Specifies <code>CustomEvent.detail</code>. This value may be
+           <code>null</code>.
+          </p>
+         </descr>
+        </param>
+       </parameters>
+
+       <returns type="void">
+        <descr>
+         <p>
+<!--empty paragraph-->
+         </p>
+        </descr>
+       </returns>
+
+       <raises>
+<!-- No exceptions -->
+       </raises>
+      </method>
+     </interface>
 <!-- Event target interface -->
      <interface name="EventTarget" id="Events-EventTarget" since="DOM Level 2">
       <descr>
@@ -5546,15 +5651,16 @@
 
         <p>
          This is a general event for notification of all changes to the
-         document. It can be used instead of the more specific events
-         listed below. It may be dispatched after a single modification
-         to the document or, at the implementation's discretion, after
-         multiple changes have occurred. The latter use should generally
-         be used to accommodate multiple changes which occur either
-         simultaneously or in rapid succession. The target of this event
-         is the lowest common parent of the changes which have taken
-         place. This event is dispatched after any other events caused
-         by the mutation(s) have occurred.
+         document. It can be used instead of the more specific mutation
+         and mutation name events listed below. It may be dispatched
+         after a single modification to the document or, at the
+         implementation's discretion, after multiple changes have
+         occurred. The latter use should generally be used to
+         accommodate multiple changes which occur either simultaneously
+         or in rapid succession. The target of this event is the lowest
+         common parent of the changes which have taken place. This event
+         is dispatched after any other events caused by the mutation(s)
+         have occurred.
         </p>
        </def>
       </gitem>
@@ -5637,7 +5743,9 @@
 
            <td>
             <code>MutationEvent.relatedNode</code> holds the parent node
-            of the node being inserted.
+            of the node that has been inserted or, in case of
+            <code>Attr</code> nodes, the <code>ownerElement</code> of
+            the <code>Attr</code> node.
            </td>
           </tr>
          </tbody>
@@ -5733,7 +5841,9 @@
 
            <td>
             <code>MutationEvent.relatedNode</code> holds the parent node
-            of the node being removed.
+            of the node being removed or, in case of <code>Attr</code>
+            nodes, the <code>ownerElement</code> of the
+            <code>Attr</code> node.
            </td>
           </tr>
          </tbody>
@@ -6945,20 +7055,10 @@
         </table>
 
         <p>
-         The document, or a resource linked from it, has been loaded but
-         cannot be interpreted according to its semantic, such as an
-         invalid image, a script execution error, or non-well-formed
-         XML.
-        </p>
-
-        <ednote>
-         <edtext>
-          See open issues
-          <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/15'>ISSUE-15</loc>
-          and
-          <loc href='http://lists.w3.org/Archives/Member/member-webapi/2006Feb/0039'>http://lists.w3.org/Archives/Member/member-webapi/2006Feb/0039</loc>.
-         </edtext>
-        </ednote>
+         A resource failed to load, or has been loaded but cannot be
+         interpreted according to its semantics such as an invalid
+         image, a script execution error, or non-well-formed XML.
+        </p>
        </def>
       </gitem>
      </glist>
@@ -7489,112 +7589,6 @@
       </gitem>
      </glist>
     </div3>
-
-    <div3 id="Events-eventgroupings-customevents">
-     <head>
-      Custom event types
-     </head>
-
-     <p>
-      @@@
-     </p>
-
-     <definitions>
-<!-- MutationEvent interface -->
-      <interface name="CustomEvent" inherits="Event" id="Events-CustomEvent" since="DOM Level 3">
-       <descr>
-        <p>
-         @@@
-        </p>
-
-        <p>
-         To create an instance of the <code>CustomEvent</code>
-         interface, use the
-         <code>DocumentEvent.createEvent("CustomEvent")</code> method
-         call.
-        </p>
-       </descr>
-
-       <attribute id="Events-CustomEvent-detail" name="detail" type="DOMObject" readonly="yes">
-        <descr>
-         <p>
-          Specifies some detail information about the
-          <code>Event</code>.
-         </p>
-        </descr>
-       </attribute>
-
-       <method name="initCustomEventNS" id="Events-Event-initCustomEventNS">
-        <descr>
-         <p>
-          The <code>initCustomEventNS</code> method is used to
-          initialize the value of a <code>CustomEvent</code> object and
-          has the same behavior as <code>Event.initEventNS()</code>.
-         </p>
-        </descr>
-
-        <parameters>
-         <param name="namespaceURI" type="DOMString" attr="in">
-          <descr>
-           <p>
-            Refer to the <code>Event.initEventNS()</code> method for a
-            description of this parameter.
-           </p>
-          </descr>
-         </param>
-
-         <param name="typeArg" type="DOMString" attr="in">
-          <descr>
-           <p>
-            Refer to the <code>Event.initEventNS()</code> method for a
-            description of this parameter.
-           </p>
-          </descr>
-         </param>
-
-         <param name="canBubbleArg" type="boolean" attr="in">
-          <descr>
-           <p>
-            Refer to the <code>Event.initEventNS()</code> method for a
-            description of this parameter.
-           </p>
-          </descr>
-         </param>
-
-         <param name="cancelableArg" type="boolean" attr="in">
-          <descr>
-           <p>
-            Refer to the <code>Event.initEventNS()</code> method for a
-            description of this parameter.
-           </p>
-          </descr>
-         </param>
-
-         <param name="detailArg" type="DOMObject" attr="in">
-          <descr>
-           <p>
-            Specifies <code>CustomEvent.detail</code>. This value may be
-            <code>null</code>.
-           </p>
-          </descr>
-         </param>
-        </parameters>
-
-        <returns type="void">
-         <descr>
-          <p>
-<!--empty paragraph-->
-          </p>
-         </descr>
-        </returns>
-
-        <raises>
-<!-- No exceptions -->
-        </raises>
-       </method>
-      </interface>
-     </definitions>
-    </div3>
    </div2>
   </div1>
 <!--
@@ -10745,26 +10739,6 @@
     <bibref ref="ECMAScript"/> binding for the Level 3 Document Object
     Model Events definitions.
    </p>
-
-   <ednote>
-    <edtext>
-     There a some open issues regarding clarifications around terms such
-     as 'read-only',
-     <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/24'>ISSUE-24:
-     DOM3EV: DontDelete and other internal properties</loc>,
-     <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/23'>ISSUE-23:
-     DOM3EV: passing non-Strings to String methods</loc>,
-     <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/22'>ISSUE-22:
-     DOM3EV: Define what "read-only" means for ECMAScript</loc>, and see
-     also
-     <loc href='http://www.w3.org/mid/[email protected]'>Proposed
-     rewrite of DOM3EV Appendix E</loc>,
-     <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/21'>ISSUE-21:
-     Should we use RFC 2119 keywords keywords consistently to state
-     conformance requirements?</loc>; see also
-     <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/13'>ISSUE-13</loc>.
-    </edtext>
-   </ednote>
 <!--
     ******************************************************
     | Events ECMA SCRIPT BINDINGS                         |
@@ -11593,11 +11567,11 @@
      http://msdn.microsoft.com/scripting/default.htm
     </bibl>
 
-    <bibl id="KeyEvent" key="KeyEvent for Java" href="http://java.sun.com/j2se/1.4.1/docs/api/java/awt/event/KeyEvent.html">
+    <bibl id="KeyEvent" key="KeyEvent for Java" href="http://java.sun.com/j2se/1.4.2/docs/api/java/awt/event/KeyEvent.html">
      <titleref>Java 2 SDK, Standard Edition Documentation, Version
-     1.4.1, Class java.awt.events.KeyEvent</titleref>. Sun Microsystems.
+     1.4.2, Class java.awt.events.KeyEvent</titleref>. Sun Microsystems.
      Available at
-     http://java.sun.com/j2se/1.4.1/docs/api/java/awt/event/KeyEvent.html.
+     http://java.sun.com/j2se/1.4.2/docs/api/java/awt/event/KeyEvent.html.
     </bibl>
 
     <bibl id="Keys" key="Keys enumeration for .Net" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsKeysClassTopic.asp">