removing event categories and VoiceXML example, see http://lists.w3.org/Archives/Public/www-voice/2006OctDec/0052.html
--- a/source/xml-source.xml Sat Nov 18 01:54:54 2006 +0900
+++ b/source/xml-source.xml Sat Nov 18 11:16:22 2006 +0900
@@ -830,9 +830,7 @@
<p>
Event listeners can be registered on all nodes in the tree for a
- specific type of event (<specref ref="Event-types"/>) or event
- category (<specref ref="Events-EventTypes-category"/>), and
- phase.
+ specific type of event (<specref ref="Event-types"/>), and phase.
</p>
<p>
@@ -871,8 +869,7 @@
<olist>
<item>
<p>
- they were registered for the same type of event, or the same
- category.
+ they were registered for the same type of event
</p>
</item>
@@ -1097,26 +1094,6 @@
are in no namespace.
</p>
- <div3 id="Events-EventTypes-category">
- <head>
- Event types and event categories
- </head>
-
- <p>
- An event type could be part of one or more categories. A category
- is represented using a <termref def="dt-localname">local
- name</termref> and a <termref def="dt-namespaceURI">namespace
- URI</termref> as defined in <bibref ref="Namespaces11"/>. 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
- <specref ref="Events-registration-voicexmlevents"/>.
- </p>
- </div3>
-
<div3 id="Events-EventTypes-complete">
<head>
Complete list of event types
@@ -2015,12 +1992,6 @@
if desired).
</p>
</item>
-
- <item>
- <p>
- for a specific event category.
- </p>
- </item>
</ulist>
<p>
@@ -2064,49 +2035,6 @@
</p>
</div3>
- <div3 id="Events-registration-voicexmlevents">
- <head>
- Using VoiceXML Events
- </head>
-
- <p>
- In <bibref role="informative" ref="VoiceXML20"/>, event listeners
- are attached using elements:
- </p>
-<eg xml:space="preserve"><form>
- <field>
- <prompt>Please say something</prompt>
- <catch event="error.noauthorization">
- <prompt>You don't have the authorization!</prompt>
- </catch>
- <catch event="connection.disconnect.hangup">
- <prompt>Connection error</prompt>
- </catch>
- <catch event="connection.disconnect">
- <prompt>Connection error</prompt>
- </catch>
- </field>
- <catch event="error">
- <prompt>Unknown error</prompt>
- </catch>
-</form></eg>
- <p>
- Event listeners can only be registered on <code>Element</code>
- nodes, other <code>Node</code> types are not addressable. The
- <termref def="dt-target-phase">target phase</termref> and the
- <termref def="dt-bubbling-phase">bubbling phase</termref> are
- coupled during the registration.
- <bibref role="informative" ref="VoiceXML20"/> does not address
- namespaces in event types but uses the notion of event categories.
- The event type <code>"connection.disconnect.hangup"</code> could
- be associated to the event categories
- <code>{"http://www.example.org/2003/voicexml",
- "connection"}</code> and
- <code>{"http://www.example.org/2003/voicexml",
- "connection.disconnect"}</code>.
- </p>
- </div3>
-
<div3 id="Events-registration-html40">
<head>
Using XML or HTML attributes