Roland Merrick wrote:
I have changed the abstract.
Greetings Shane, a few comments :
We ought to introduce early, perhaps
the Abstract, the notion that we are defining three "features"
that are related, events, handlers and script.
Actually I removed it. This is a good change - we don't need a note
2.3.Host Language Processor Conformance
Host Language Processor vs. User Agent
We have historically called this user
agent conformance, but since XML Events 2 is a generic XML Events
we really need to specify conformance for all classes of processors.
===== an editor note for now.
Historical. I have removed it.
Why is the following interesting, necessary
that observer = "<element-id>" and event = "<event-type>"
are similar to the begin = "<element-id>.<event-type>"
attribute in SMIL EventTiming [SMIL20].
Turned into a more complete example
we have lots of examples ( 3.1.1 ),
why include a partial example here? If we do want to, then lets make it
more "complete", i.e. not jusr "where 'para1' is some ancestor
of the following node"
You provided new text for this separately, which has now been
this is confusing, both DOM2 and DOM
3 only define 3 phases: capture, target, bubble. What does
mean and how would it be expressed in terms of DOM3 (and for that
We then go on to define the ' default
behavior is phase="default" ', which I interpret as meaning if
you omit the attribute it is the equivalent of having specified
This may be the same as XML Events (1)
but that isn't clear either.
comment is also relevant to Handler
feature : addEventListener, removeEventListener
So are you suggesting we add those attributes to the events attribute
4.The XML Handlers Module
I suspect that host language may wish
to allow @if and @while on custom actions in the host language.
Regardless, I have integrated the other changes and put up a new draft
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: firstname.lastname@example.org