The Microsoft Web Stack: from client/server to client/Web-Stack/server. This ppt has many transforms and layers, an dis meant to test slideshare. The presentation itself is based on the results of our participation in the Massachusetts ODF Pilot Study, where we found that the barrier to implementing ODF was a proliferation of workgroup related MSOffice bound business processes.
Significantly, the ODF vs OOXML argument is more about replacing costly MSOffice licenses with freely available OpenOffice than anything else. The XML formats themselves are application specific and not interchangeable. Least ways not without a significant loss of "presentation" fidelity and business process logic. Because OpenOffice-ODF and MSOffice-OOXML are application specific to the core, the da Vinci group moved from ODF to W3C CDF (XHTML-CSS-SVG-Xforms in an .ePUB container).
The advantages of this move to CDF are threefold; it's application independent, designed for interoperability and interchange, and most importantly, web ready.
While it's beyond difficult to perfect a high fidelity conversion between two application specific formats, it's much easier to perfect a conversion between an application specific format and a generic, application independent format. By converting MSOffice and OpenOffice documents to CDF, it is possible to achieve that higher level of interoperability end users seek.
This presentation outlines the MS Web-Stack strategy, which is based on advantageous but proprietary interop with MSOffice and Outlook. Key to this plot is MSOffice-OOXML becoming an ISO standard.
In the December 2007 release of the MSOffice SDK beta (date of this presentation is September 2007), Microsoft provided an easy to implement API for the high fidelity conversion of MSOffice-OOXML docs to XAML.
XAML "fixed/flow" is part of the proprietary WPF (Windows Presentation Foundation layer) that also includes Silverlight, XPS, Smart Tags and LINQ. These are proprietary alternatives to XHTML, CSS, SVG, XForms, RDF, SPARQL, PDF and SWF (Flash).
ISO approval of MSOffice-OOXML in March of 2008 establishes MSOffice as a standards compliant "editor", effectively shielding the Microsoft WPF proprietary technologies from anti trust charges. Since MSOffice-OOXML is now an ISO standard, competitors are free to do their own conversions to open Web formats like (X)HTML-CSS.
There is a complimentary white paper to this presentation called, "Breaking the Web to Ride the Fifth Wave". Obviously the presentation must be updated to reflect the MSOffice SDK, ISO approval, and the recent announcement of MS Live-Mesh. If SlideShare proves capable of handling the transitions and layers, i'll provide an updated version :)