Web API Working Group,
The JSR 280 (XML API for JavaTM
ME) Expert Group would like
to align
with the W3C DOM specifications to provide a subset of the DOM Core and
Events modules for the Java ME platform. We solicit the help of the Web
API group in resolving some open issues relating to the current draft
of the DOM 3 specification.
We are working with Expert Groups from other JSRs (most notably the
Scalable 2D Vector Graphics API 2.0 for Java ME and the JavaTM Language & XML User
Interface Markup Integration) to provide a DOM API subset that
precludes the need for private specialized subsets in individual JSRs.
We have put into our Proposed Final Draft specification, which we have
just submitted to the JCP, our best assessment of the desired end
states, but
due to the fact that the DOM 3 spec has not yet gone to its public
review we will have to revisit the status before we submit our Final
Approval Ballot.
We have 4 issues related to the DOM 3
specification
that we would like to resolve with the Web API group, preferably in a
time frame that would enable us to submit our Final Approval Ballot
specification to the JCP on April 2nd as currently scheduled. We would
very much appreciate your help in resolving these issues in a time
frame as close as possible to our JSR 280 release schedule.
1) MouseWheelEvent
There was a WheelEvent in the SVG spec that the SVG WG has requested be
added to DOM 3. The current status is that a substantially similar
MouseWheelEvent has been added to the current DOM 3 spec. JSR 280 will
align with the version that is approved in the DOM 3 spec; however, we
need the DOM 3 version of this API to be frozen before we can submit
our FAB specification.
2) ProgressEvent
The status is much the same as for MouseWheelEvent, except that in this
case the name proposed in the DOM 3 spec remains the same. JSR 280 will align with the version that is approved
in the DOM 3 spec; however, we need
the DOM 3
version of this API to be frozen before we can submit our FAB
specification.
3) ElementTraversal
There is a request pending to add ElementTraversal to the DOM 3 Core.
The status of this is still open ended. JSR 280 has included this
in our PFD spec submission in the hopes that we will get the addition
to DOM 3 approved, since it would facilitate the alignment of a number
of different standards. Again, we
need the DOM
3 version of this API to be frozen before we can submit our FAB
specification.
4) Event groups
Event groups were included in an earlier draft of the DOM 3 Event
specification, and have been removed from the most recent version. The
JSR 280 PFD spec has kept the
event group argument since the issue is still under discussion, but we
will remove it from our FAB spec if the elimination from the
final DOM 3 specification has been frozen in time for our FAB
submission.
Since unfortunately I have previous commitments and cannot join your
Boston meetings this week, Nandini Ramani has agreed to present these
issues on behalf of the JSR 280 Expert Group.
Thank you for your help,
Ellen Siegel
JSR 280 specification lead