hi All,

just wanted to summarize what's been harvested from the discussions and
individual input and will be taken to the Expert Group:

- it needs to be easier for the end user to specify and use an arbitrary
JAXP processor.  this has also come up in many other contexts, e.g. when
running in an application server container, individual applications need
to have more precise control of the JAXP processors they use.

- javax.xml.parsers.SAXParser and javax.xml.parsers.SAXParserFactory are
redundant with the standard XMLReader and XMLReaderFactory classes in
SAX2. SAXParser and SAXParserFactory could be deprecated.

- if DOM L3 Load/Save is standardized within the JSR's timeframe, its
implementation effectively replaces DocumentBuilder and 
DocumentBuilderFactory so they could be deprecated.

- if both of the above deprecations happen, the entire javax.xml.parsers
package could be deprecated.

- a few misc JSRs have requested small features that can be paraphrased
as more explicit and precise control of processing behavior.

- misc requests to expose some more of the Infoset.

also a note on the proposed process for the actual JSR creation, we want
to develop and markup the spec in XML.  :)  goals include explicit
markup of assertions so that a transformation could produce input for
testing and development.

thanks for all of the comments and discussions.  anyone who made, or
makes, a comment and sends me a space/time coordinate will receive a
small token of appreciation, no Java/XML swag, but something
consumable.  :)

P.S. I've also added Elliotte Rusty Harold's items from Cafe con Leche:
- spend more time on more carefully specifying what the methods already
in the javax.xml packages actually do, e.g.:
- how does the identity transform behave when transforming a DOM
Document object that has namespaced elements but no namespace
declaration attributes?
- does a SAXResult invoke startDocument() and endDocument() in its
ContentHandler when the transform only produces a document fragment?
- in general, define underspecified behavior

P.P.S. to Elliotte, I'm one of the pinheads that agrees with and
supports the inclusion of non-technical information on Cafe con Leche
and Cafe au Lait.  in these times, no matter where one stands on a
particular issue, they are so important that they need to be just as
prominent as an announcement of a bug fix for JEdit.

-- 
Jeff Suttor    <[EMAIL PROTECTED]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to