<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Joe Rubino : Architecture</title><link>http://blogs.msdn.com/jrubino/archive/tags/Architecture/default.aspx</link><description>Tags: Architecture</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Office Open XML file formats on its way to being an ISO/IEC International Standard...</title><link>http://blogs.msdn.com/jrubino/archive/2008/04/02/office-open-xml-file-formats-on-its-way-to-being-an-iso-iec-international-standard.aspx</link><pubDate>Wed, 02 Apr 2008 17:57:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8351624</guid><dc:creator>jrubino</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/jrubino/comments/8351624.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jrubino/commentrss.aspx?PostID=8351624</wfw:commentRss><description>&lt;p&gt;This is a follow up to my my post &amp;quot;&lt;a href="http://blogs.msdn.com/jrubino/archive/2008/01/12/and-now-for-something-completely-different.aspx"&gt;And now for something completely different...&lt;/a&gt;&amp;quot;.&amp;#160; Office Open XML is on its way to becoming an ISO/IEC International Standard.&amp;#160; It has received the necessary number of votes for approval as an ISO/IEC International Standard.&amp;#160; You can find out more about it here: &lt;a title="http://www.iso.org/iso/pressrelease.htm?refid=Ref1123" href="http://www.iso.org/iso/pressrelease.htm?refid=Ref1123"&gt;http://www.iso.org/iso/pressrelease.htm?refid=Ref1123&lt;/a&gt;&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8351624" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jrubino/archive/tags/Architecture/default.aspx">Architecture</category></item><item><title>And now for something completely different...</title><link>http://blogs.msdn.com/jrubino/archive/2008/01/12/and-now-for-something-completely-different.aspx</link><pubDate>Sat, 12 Jan 2008 16:26:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7089287</guid><dc:creator>jrubino</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/jrubino/comments/7089287.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jrubino/commentrss.aspx?PostID=7089287</wfw:commentRss><description>&lt;p&gt;Happy New Year!&lt;/p&gt;  &lt;p&gt;Those of you who know me, are probably aware that I worked in the State and Local Government vertical at Microsoft for a short period of time.&amp;#160; That period happened to coincide with the announcement of Massachusetts CIO Peter Quinn's initiative to mandate the use of OpenDocument format (ODF) within Massachusetts state agencies.&amp;#160; This was a huge move and frankly I never understood it.&amp;#160; Whether or not I understood it, it caused my colleagues and myself a ton of pain.&lt;/p&gt;  &lt;p&gt;Yes, I am a Microsoft employee and yes I have allegiance to Microsoft, but why would a politician push a document format?&amp;#160; I just could not relate.&amp;#160; Especially since after briefly reviewing ODF, I felt it was not sufficient to handle complex documents that we have grown used to.&amp;#160; &lt;/p&gt;  &lt;p&gt;So I was thrilled to see the new report &amp;#8220;What&amp;#8217;s Up .Doc? ODF, Open XML and the Revolutionary Implications of XML in Productivity Applications.&amp;#8221;&amp;#160; The full 40+ page document can be accessed on the Burton Group website here: &lt;a href="http://www.burtongroup.com/Guest/Ccs/WhatsUpDoc.aspx"&gt;http://www.burtongroup.com/Guest/Ccs/WhatsUpDoc.aspx&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Some notable findings within the report:&lt;/p&gt;  &lt;p&gt;&amp;#183; The report underscores the rationale for multiple document standards, stating that ODF and Open XML were developed out of different design considerations and priorities and therefore are not &amp;#8220;interchangeable.&amp;#8221;&lt;/p&gt;  &lt;p&gt;&amp;#183; The authors describe Open XML as &amp;#8220;considerably more expressive&amp;#8221; and &amp;#8220;more eco-system and application oriented&amp;#8221; than ODF, citing its support for custom schema and full-fidelity round-tripping of documents created in Microsoft Office applications. The report predicts both on the basis of functionality supported and a rich ecosystem, Open XML will be more successful and &amp;#8220;more pervasive&amp;#8221; than ODF.&lt;/p&gt;  &lt;p&gt;&amp;#183; Open XML adoption is projected to be widespread and swiftly fuelled by an ecosystem supporting Microsoft Office applications. In contrast, the report contends that ODF evolution will be &amp;#8220;slow and complex&amp;#8221;, largely on account of Sun&amp;#8217;s ownership of OpenOffice.org, the primary implementation of ODF in the market.&lt;/p&gt;  &lt;p&gt;&amp;#183; Examination of ODF leads the authors to conclude that ODF is &amp;#8220;insufficient for real-world enterprise requirements&amp;#8221; and its use will be limited to scenarios where there are no requirements around complex document modeling or document fidelity with Microsoft Office applications.&lt;/p&gt;  &lt;p&gt;&amp;#183; Burton Group&amp;#8217;s overarching recommendation is to exploit Open XML&amp;#8217;s capabilities and use ODF &amp;#8220;by exception rather than by default.&amp;#8221;&lt;/p&gt;  &lt;p&gt;So this is something completely different from what I work on everyday, but it is important to architects so that is why decided to blog about it.&amp;#160; If you are fighting a battle around ODF and Open XML, definitely check out this document.&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7089287" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jrubino/archive/tags/Architecture/default.aspx">Architecture</category></item></channel></rss>