TextGlow, the prototype Open XML Viewer for Silverlight is one of the most popular posts in the brief history of my blog. Intergen, a Microsoft partner in New Zealand, have now elected to offer the source code for this application on OpenXMLDeveloper.org. I am very excited about this development, Silverlight is amazing, and the combination of Open XML and Siverlight easy for a nerd like me to get excited about.

If you haven't signed up for OpenXMLDeveloper.org, now is a good time to do so. You'll find this source code as well as other projects to help your development of Open XML solutions.

Here is an excerpt from the article:

Displaying Open XML documents in Silverlight with TextGlow
By James Newton-King

The Office Open XML file format has opened up a new range of possibilities to working with documents. The Microsoft Office 2007 suite of products replaces the old binary formats and produces documents in a parser friendly XML format by default instead.

TextGlow (www.textglow.net) is a Silverlight 2.0 application that leverages the new Office Open XML file format to display Word documents directly in the browser. This article will look at how to use the built-in features of Silverlight 2.0 to read content from an OpenXML package, parse XML using LINQ to XML and display the document contents using Silverlight.

In case you missed it yesterday, DAISY Consortium announced the release of the second version of the DAISY Translator for Word.

I've said it a few times on my blog, but I did want to say again how much we value our partnership with the DAISY Consortium, and our gratitude towards them for their help on this work. Microsoft Office is the leader in providing accessibility support in business productivity software; we are committed to continuous improvement of our support for users with disabilities.

From the press release: "Michael Hingson, the President of The Hingson Group, believes that the "DAISY navigation system is one of the most significant developments to be made available since the development of Braille. DAISY allows people who are blind to move around recorded and electronic documents easily and seamlessly in a way so far only available to sighted readers."

The big news with the 2.0 release is the addition of Full DAISY Text and Audio books. Instead of converting to a DAISY XML file, you can now effectively save your Word documents as MP3 files. DAISY XML files can be read natively by some DAISY players, and the DAISY Pipeline is still available for processing those XML files. For more technical readers, this means that Version 2.0 of the translator incorporates the "Lite" version of the DAISY Pipeline, and generates full text and audio books using the Text-to-Speech service on your PC.

But the change to the 2.0 release of the Translator for Word represents a monumental simplification of this process. This is a fantastic development.

Figure 1: Screen shot of the Word Save As DAISY 2.0 Dialog Box

As part of this activity, a new web-based player is available for DAISY Talking books. Buttercup has been developed through a partnership between DAISY, Microsoft and New Zealand's Intergen to allow people to listen to & navigate DTB's through a browser via a Silverlight control.

I have also attached a full-audio full-text book of this post. This book was created only by using the translator. You can download this ZIP file, and open it with the Buttercup player. No other software than Word 2007, Vista (the TTS engine) and the translator are required to create this talking book.

If you are interested in learning more about DAISY Talking book formats, a good description has been added to the DAISY.org forums.

I would like to thank the DAISY Consortium, George Kerscher, Intergen Software, Sonata Software, and the Adaptive Technology experts from the Royal New Zealand Foundation for their support on the project.

Just keeping tabs on the state of matters for document format standards. I thought I'd share some of those interesting data points and connect some dots along the way.

Ouch. Rich Jelliffe discusses some of the dynamics of the OASIS ODF TC.

Rick says: "It seems that OASIS rules actually ban Technical Committee members from participating on the comments list with non-committee members. Communication is a one-way affair, an offering to silent gods. …

It didn't used to be this way. And snooping around the archives, it seems that when the rules were changed (by the then OASIS board) in 2003, there was quite a stink. The justification was to prevent spam: I cannot quite understand the logic, but the effect is that it meant if you want to participate at OASIS you have to pay."

I don't pretend to understand the inner workings of standards organizations, but I definitely recall some very sharp criticism of Microsoft and ECMA for some very similar reasons. Does this mean the withdraw of IBM from OASIS is imminent? J It's also strange how, when faced with criticism, some individuals revert to Microsoft-bashing as a means to defending their own actions. So then let me revert to some old habits and point out an apparent contrast between the words written in a different forum:

"Those who control the exchange format, can control interoperability and turn it on or off like a water faucet to meet their business objectives." – this from the chair of the ODF TC.

Interesting: Alex Brown (a while ago, I know) drills on conformance issues for ODF 1.2 and exposes a fairly basic and problematic reality. Rick had a little to say about this as well.

This is an extension of the discussion that is exemplified by Oracle's comment on Open XML conformance during the BRM process, and those of Google as well. It seems that after all this time we're not settled on basic questions, for example whether or not all content within the ZIP package should be described using XML. Again I don't pretend to have an answer, but appreciate the level of attention that Open XML has brought to this problem.

The University of Illinois Law has published a paper on the (recent, but somewhat aged) state of interoperability for Open XML and ODF. It isn't a glowingly positive report for either standard, but it is based on older implementations, and by virtue of the fact that the numbers in the tables seem higher for Open XML than they do ODF, one could regard that as a "win" for Open XML. I think the bigger message is that for both Open XML and ODF, things are improving. In the long view, this report isn't surprising. In the 20+ year history of desktop business productivity applications, it is reasonable to expect a long ramp for interoperability for brand new document formats. I would like to raise my hand on this with a few questions:

Why isn't anyone talking about PDF? – seems like if one wanted to discuss document exchange, PDF would be an interesting basis for comparison. For example, how likely are various PDF Viewing applications to get it "right" when opening a PDF file? What is the degree of variance across the thousands of PDF generation implementations in the world? Odd that people seem to have vacated that space very quickly. The warm fire around which folks are huddled seems to be the one where people have a hope of editing.

Why isn't anyone talking about binary documents? – I hate to draw attention to a white elephant, but the use of binary document formats (at least by count of what is indexed on the web) is on the order of ~200,000 to 200,000,000. I would love to see an amendment to this study which illustrates the interoperability of binary documents in the same test.

And for all this, here's the point:

The rough edges of document format interoperability are apparent. One should question the fastest way to get to the goal of high quality inter application document exchange. It would seem that (reference above) that a wealth of IQ is being devoted to evolving standards to achieve the lofty goals that are floating around this topic; lots and lots of paint is being used for boxing things into tight corners.

For the folks who don't appreciate the handfighting and procedural aspects to the standards work, though, how can they get any benefit out of this? If it is the case that "the little guy" isn't welcome at the table in the standards discussion (which I don't believe is the case for Open XML or ODF), what is the fastest means to high-quality document exchange?

As far as I can see, only one vendor is doing this: http://www.documentinteropinitiative.org. I have not found this documentation from other developers: http://www.documentinteropinitiative.org/ECMA-376/reference.aspx, http://www.documentinteropinitiative.org/OASISODF1.1/reference.aspx. I am hopeful to see other vendors bringing this data to the table, beyond their participation in DII and on OpenXMLDeveloper.org. I hope to see this because it helps folks sort through the real problems vs. those that are less significant, and helps ensure that we're really talking about document format exchange, rather than hopeful RFP checkbox filling.

I am optimistic for the future and hopeful for more developer-to-developer engagement on real product implementations. I think it matters a great deal for this transition to standardized document formats.