<?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>No license needed to use the Office Open XML formats</title><link>http://blogs.msdn.com/brian_jones/archive/2006/08/04/688932.aspx</link><description>I still get folks asking me questions about the licensing of the Open XML formats from time to time, and it seems there is a lot of misinformation out there. It's actually been well over 7 months since we made the move away from licensing the formats</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: No license needed to use the Office Open XML formats</title><link>http://blogs.msdn.com/brian_jones/archive/2006/08/04/688932.aspx#689541</link><pubDate>Sat, 05 Aug 2006 18:48:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:689541</guid><dc:creator>hAl</dc:creator><description>Thanks for clearing that up Brian. &lt;br&gt;I would suggest Microsoft puts up a simularly comprehensible short statement on it's website when the format is ready. </description></item><item><title>Baker &amp;amp;amp; McKenzie paper on Open XML</title><link>http://blogs.msdn.com/brian_jones/archive/2006/08/04/688932.aspx#691049</link><pubDate>Mon, 07 Aug 2006 19:04:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:691049</guid><dc:creator>Doug Mahugh</dc:creator><description>Baker &amp;amp;amp;amp; McKenzie's London office has pubished a paper on the Open XML formats and the Ecma standardization...</description></item><item><title>re: No license needed to use the Office Open XML formats</title><link>http://blogs.msdn.com/brian_jones/archive/2006/08/04/688932.aspx#694101</link><pubDate>Thu, 10 Aug 2006 09:34:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:694101</guid><dc:creator>Filip Verhaeghe</dc:creator><description>Slightly off topic, but it occured to me that Microsoft could really help the .docx standard by adding support for it in the ASP.NET toolbox components. &lt;br&gt;&lt;br&gt;For instance, a free to use docx viewer component would be amazing to allow people to use Word to create a document just the way they like it, and then upload the document AS IS to the corporate website. An ASP.NET page could load the document in the DOCX viewer component, and suddenly everyone can create content for the web in an environment they know. &lt;br&gt;&lt;br&gt;The nice thing about ASP.NET is that it generates HTML. This approach would also provide a client platform-free viewer for Microsoft's XML standard. Government saying they want to expose their internal information to the public in a simple way, would need to look at Microsoft's DOCX is the easiest way to do so. I realise that fidelity in HTML cannot be 100%, but XAML will remedy that in the future. In later versions of the standard ASP.NET block, Microsoft can provide intra-component checking for the available platform (XAML or not), and adjust accordingly. The whole world would dynamically change over to using XAML simply by recompiling their ASP.NET sites with the lastest version of Visual Studio.&lt;br&gt;&lt;br&gt;Putting just 1 internal Microsoft person on such a project would make a lot of difference to the whole world. It seems to me like one of the best ways to create a free Word viewer (you might hear people asking for a PPTX viewer next :-)).&lt;br&gt;&lt;br&gt;Filip.&lt;br&gt;</description></item><item><title>Questions on Open XML</title><link>http://blogs.msdn.com/brian_jones/archive/2006/08/04/688932.aspx#3997333</link><pubDate>Sun, 22 Jul 2007 14:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3997333</guid><dc:creator>Wouter van Vugt</dc:creator><description>&lt;p&gt;For those of you not only reading my blog, but also the other content provided by the Info Support blog&lt;/p&gt;
</description></item></channel></rss>