I'm a few days late in reporting that the first public working draft of the Efficient XML Interchange (EXI) format is now available from W3C. And, naturally, the "binary XML" threads have resumed on xml-dev and in a few other places.
In an earlier blog entry I talked about a discussion to extend the StAX API with XML data types. The discussion is still ongoing and we have actually written some Java interfaces to solidify our ideas.
This is a great example of how your opinion counts and how a community can work together to improve a product. We kept hearing from many of you about how good the Woodstox XML parser was, especially how well it performed.
The W3C Efficient XML Interchange (EXI) Performance Testing Framework is now publicly available for download. This is the testing framework used by the EXI WG to evaluate properties of "binary XML" candidates.
Two months after releasing JAXP RI version 1.4.1, we are now releasing version 1.4.2.
This is therefore the second update release to the FCS version from last year that is also part of JDK 6.
A discussion has been started in the email@example.com mailing list about typed extensions to the StAX API. We hope this discussion will serve as the basis for a proposal to be incorporated in the next release of the API. Subscribe to the mailing list (it is moderated) if you are interested in influecing this next-gen API.
The JAXP 1.4.1 RI is now available. This is an update release to the FCS version that we released a few months back, and that is also included in JDK 6.0. The change log shows that approximately 36 issues have been addressed in this release.
It's been a while since the last time I blogged about Japex. Over the last year or so there have been many incremental improvements (resulting in 30 different releases) and with the recent addition of combined bar charts, I thought it was time to make this the official 1.1 release.
A few people have found problems validating DOM instances with JAXP1.4/JDK 6.0. I saw this quesion raised in the Java Technology and XML forum, and at least 3 bugs were filed for this in the last few weeks. I'll use this blog entry to explain what the problem is and how to easily fix your code.