reflect what's now on qa-dev.w3.org
authorbjoern
Mon, 03 Dec 2007 16:54:51 +0900
changeset 44 52eeb7597681
parent 43 19cf470833b8
child 45 d21be64c3e18
reflect what's now on qa-dev.w3.org
source/xml-source.xml
--- a/source/xml-source.xml	Mon Dec 03 12:00:39 2007 +0900
+++ b/source/xml-source.xml	Mon Dec 03 16:54:51 2007 +0900
@@ -619,81 +619,66 @@
      </head>
 
      <p>
-      (This section is currently being rewritten.)
+      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>.
+      For additional information about
+      <xspecref href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance">conformance</xspecref>,
+      please see the DOM Level 3 Core specification
+      <bibref ref="DOMCore"/>.
      </p>
 
      <p>
       An implementation is DOM Level 3 Events conformant if it supports
       the Core module defined in <bibref ref="DOM2Core"/>, the
-      <specref ref="Events-flow"/> and the interfaces with their
-      associated semantics defined in <specref ref="Events-interface"/>.
-      An implementation conforms to a DOM Level 3 Events module if it
-      conforms to DOM Level 3 Events and the event types defined in the
-      module. An implementation conforms to an event type if it conforms
-      to its associated semantics and DOM interfaces. For example, an
-      implementation conforms to the DOM Level 3 User Interface Events
-      module (see <specref ref="Events-eventgroupings-uievents"/>) if it
-      conforms to DOM Level 3 Events (i.e. implements all the basic
-      interfaces), can generate the event types
-      <termref def="event-DOMActivate">DOMActivate</termref>,
-      <termref def="event-DOMFocusIn">DOMFocusIn</termref>,
-      <termref def="event-DOMFocusOut">DOMFocusOut</termref>,
-      <termref def="event-focus">focus</termref>, and
-      <termref def="event-blur">blur</termref> accordingly to their
-      semantics, supports the <code>UIEvent</code> interface, and
-      conforms to the DOM Level 2 Core module.
+      <specref ref="Events-flow"/> mechanism and the interfaces with
+      their associated semantics defined in
+      <specref ref="Events-interface"/>. An implementation conforms to a
+      DOM Level 3 Events module if it conforms to DOM Level 3 Events,
+      the event types defined in the module, and the modules the module
+      depends upon (if any).
      </p>
 
-     <note>
-      <p>
-       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
-       <code>DocumentEvent.createEvent()</code> method and dispatch an
-       event type associated with this interface using the
-       <code>EventTarget.dispatchEvent()</code> method.
-      </p>
-     </note>
+     <p>
+      An implementation conforms to an event type if it conforms to its
+      associated semantics and DOM interfaces. This includes that event
+      objects that are generated by the implementation are generated as
+      outlined in the tabular definition of the event type.
+     </p>
+
+     <p>
+      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
+      <code>DocumentEvent.createEvent()</code> method and dispatch an
+      event type associated with this interface using the
+      <code>EventTarget.dispatchEvent()</code> 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 <bibref ref="DOM2Core"/> and use the
-      <specref ref="Events-flow"/>. For additional information about
-      <xspecref href="http://www.w3.org/TR/DOM-Level-3-Core/introduction.html#ID-Conformance">conformance</xspecref>,
-      please see the DOM Level 3 Core specification
-      <bibref ref="DOMCore"/>. DOM Level 3 Events is built on top of DOM
-      Level 2 Events <bibref ref="DOM2Events"/>, 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>.
+      Level 3 Events is supported by the implementation. Since DOM Level
+      3 Events is built on top of DOM Level 2 Events
+      <bibref ref="DOM2Events"/>, an implementation that returns
+      <code>true</code> for <code>"Events"</code> and <code>"3.0"</code>
+      will also return <code>true</code> for the parameters
+      <code>"Events"</code> and <code>"2.0"</code>. The same holds for
+      the feature strings defined for the individual event modules as
+      applicable. Refer to
+      <xspecref href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMFeatures">DOM
+      Features</xspecref> in <bibref ref="DOMCore"/> for additional
+      information.
      </p>
-
-     <p>
-      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>
 
@@ -12660,17 +12645,6 @@
    </p>
 
    <blist>
-    <bibl id="Charmod" key="CharModel" href="http://www.w3.org/TR/2003/WD-charmod-20030822/">
-     <titleref>Character Model for the World Wide Web 1.0</titleref>, M.
-     D&#252;rst, F. Yergeau, R. Ishida, M. Wolf, T. Texin, Editors.
-     World Wide Web Consortium, August 2003. This version of the
-     Character Model for the World Wide Web Specification is
-     http://www.w3.org/TR/2003/WD-charmod-20030822/. The
-     <loc href="http://www.w3.org/TR/charmod/">latest version of
-     Character Model</loc> is available at
-     http://www.w3.org/TR/charmod/.
-    </bibl>
-
     <bibl id="DOM2Core" key="DOM Level 2 Core" href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113">
      <titleref>Document Object Model Level 2 Core
      Specification</titleref>, A. Le Hors, et al., Editors. World Wide