User: jpmcc Date: 2008-04-07 11:00:59+0000 Modified: marketing/www/planet/atom.xml marketing/www/planet/index.html marketing/www/planet/opml.xml marketing/www/planet/rss10.xml marketing/www/planet/rss20.xml
Log: Planet run at Mon Apr 7 12:00:15 BST 2008 File Changes: Directory: /marketing/www/planet/ ================================= File [changed]: atom.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/atom.xml?r1=1.300&r2=1.301 Delta lines: +29 -20 --------------------- --- atom.xml 2008-04-07 05:00:34+0000 1.300 +++ atom.xml 2008-04-07 11:00:55+0000 1.301 @@ -5,9 +5,36 @@ <link rel="self" href="http://marketing.openoffice.org/planet/atom.xml"/> <link href="http://marketing.openoffice.org/planet/"/> <id>http://marketing.openoffice.org/planet/atom.xml</id> - <updated>2008-04-07T05:00:27+00:00</updated> + <updated>2008-04-07T11:00:47+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> + <entry xml:lang="en"> + <title type="html">The ugliness of it all</title> + <link href="http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/"/> + <id>http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/</id> + <updated>2008-04-07T10:23:07+00:00</updated> + <content type="html"><p>I shall not complain that much about what happened with OOXML. In fact, the act of standardizing OOXML has not really brought any significant advantages to OOXML. ODF is an ISO standard and so is OOXML. That&#8217;s what I call a draw, and Microsoft has been battling hard for a bloody draw, as in the end, <a href="http://www.ft.com/cms/s/0/c9743360-01a8-11dd-a323-000077b07658.html?nclick_check=1">the word has spread and everybody now knows about the insane amount of pressures Microsoft has applied to the ISO, the IEC, the ITTF and the national standards bodies</a>. But what will be the outcome of all this? Let me outline the following steps in Microsoft&#8217;s strategy in regard of standardization. This can be described as a pincer movement.</p> +<p> First, Microsoft will try to kill ODF. They can try to do this at two levels: at the level of the OASIS ODF TC, and at the level of the next iteration of ODF, ODF 1.2 (due sometimes this Fall and later to be brought on to the ISO). You can rest assured that Microsoft will exert pressures on the OASIS ODF committees either by attempting to stuff it, or by pressuring players such as Novell, Patrick Durusau, or even Sun Microsystems. One of them is a puppet of Microsoft, bound by heavy investment of Microsoft disguised as a legal and business partnership agreement (Novell), <a href="http://www.robweir.com/blog/2008/03/contra-durusau-part-1.html">another one made an odd trip not that far from Redmond</a> and came back with a completely new view on OOXML and ODF (P. Durusau), while another one has a strong legal settlement with Microsoft and may not afford to lose it for obvious business reasons (Sun). </p> +<p> Another way for Microsoft to attack ODF would be to oppose the standardization of ODF 1.2. They will use the same tactics they had with OOXML, but in the opposite direction. It will be funny to watch how the ISO and the national standards bodies will switch all of a sudden to a demanding stance on ODF 1.2, <span class="Apple-style-span">which will only be an iteration of an existing ISO standard. </span>I am afraid we will witness such a shocking twist in the standardization bodies&#8217; attitude. Romania, for instance, might completely change its happy-go-merry stance it had on OOXML (Approve without comments, twice) to an eagle-eye, unforgiving and watchdoggish scowl of ODF (Disapprove with&#8230; interesting comments). Heck, they might even use their former &#8220;laxist&#8221; attitude they had with OOXML as an excuse to block ODF, those masters of cynicism. </p> +<p> But all this is just one wing of  the pincer movement I am describing here. The other part of the strategy was however clear ever since the beginning. OOXML is the first chapter into an attempt by Microsoft to shove its own technologies to the ISO. Next in line will be XPS. If you don&#8217;t know what XPS is, <a href="http://www.microsoft.com/whdc/xps/default.mspx">check it out from the source</a>. Yes, you got that right. PDF reloaded. Now with more patents, OOXML dependencies, and legal traps. What&#8217;s the advantage you ask? None. But the respectable industry players we saw in every national standards body (understand: Microsoft&#8217;s partners) will insist that it will offer them <span class="Apple-style-span">clarity </span>and a potential new source of <span class="Apple-style-span">revenue. </span>This time though Microsoft got really clever: They went where Adobe had forgotten to go for ages, to the printing industry. This time we will see HP really coming out with flowers for Redmond. In France , HP never joined the works of our committee but they got really supporting of OOXML all of a sudden, around Friday night and after somebody  (obviously being married to a woman of Italian descent with a nice hat, blue eyes, brown hair, ) had been given instructions to play nice with Microsoft. What you say, &#8220;<span class="Apple-style-span">is the French government bending to the will of Microsoft? Is it weaker than corporations?&#8221; </span>Depends whom you ask, who you can contact, and who you supported. Enough said. Back to XPS. </p> +<p>Well XPS is, believe or not, a standard in the making. And since it is being &#8220;<a href="http://www.ecma-international.org/memento/TC46.htm">developed</a>&#8221; (ah, the game of mirrors, illusions and appearances) by the Ecma, it will be pushed through the very same Fast-Track process the Ecma has been lavishly endowed to use with OOXML. </p> +<p> Would you believe me if I wrote that I knew what&#8217;s in store after XPS? Let&#8217;s bet I know it. After OOXML shall come XPS. And once Microsoft will have locked the whole industry with its document formats, they will try to do the same with multimedia formats. Expect the future Windows Media formats, their proprietary video codecs to follow the same path. Their glue shall be Silverlight, which in turn rests on Windows Presentation Foundation and the .NET framework. The license shall be the famous OSP, effectively barring GPL implementations and leaving many other issues, such as the RAND mode applied on the covered technologies, in the shadows, but always as a critical factor to consider. Novell will follow, as usual, with incomplete and patent-riddled implementations that you will only be able to safely use with Novell products. </p> +<p> And then? Then,  as Shakespeare once magnificently wrote, then there shall be <span class="Apple-style-span">silence. </span>At last, silence to win, silence to dominate, silence to influence, silence to pressure, and silence to silence them all. <span class="Apple-tab-span"> </span> </p> +<p class="akst_link"><a href="http://standardsandfreedom.net/?p=59&amp;akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_59" class="akst_share_link" rel="nofollow">Share This</a> +</p></content> + <author> + <name>Charles Schulz</name> + <uri>http://standardsandfreedom.net</uri> + </author> + <source> + <title type="html">Moved by Freedom - Powered by Standards » OOo Postings</title> + <subtitle type="html">A weblog by Charles-H. Schulz.</subtitle> + <link rel="self" href="http://standardsandfreedom.net/index.php/category/ooo-postings/feed"/> + <id>http://standardsandfreedom.net/index.php/category/ooo-postings/feed</id> + <updated>2008-04-07T11:00:19+00:00</updated> + </source> + </entry> + <entry> <title type="html">MS answers to Master Thesis</title> <link href="http://lodahl.blogspot.com/2008/04/ms-answers-to-master-thesis.html"/> @@ -364,7 +391,7 @@ <subtitle type="html">A weblog by Charles-H. Schulz.</subtitle> <link rel="self" href="http://standardsandfreedom.net/index.php/category/ooo-postings/feed"/> <id>http://standardsandfreedom.net/index.php/category/ooo-postings/feed</id> - <updated>2008-04-03T05:00:17+00:00</updated> + <updated>2008-04-07T11:00:19+00:00</updated> </source> </entry> @@ -515,22 +542,4 @@ </source> </entry> - <entry> - <title type="html">LinuxTag 2008 with OpenOffice.org "mini conference"</title> - <link href="http://ooomarketing.blogspot.com/2008/03/linuxtag-2008-with-openofficeorg-mini.html"/> - <id>tag:blogger.com,1999:blog-4887643299605448632.post-4184165243450780018</id> - <updated>2008-03-26T15:30:32+00:00</updated> - <content type="html">At this year's LinuxTag, OpenOffice.org will host it's own "mini conference" (not to be confused with the official OpenOffice.org Conference). Several well-known project members will deliver speeches and lectures about OpenOffice.org, it's programmability, the ongoing migrations, the OpenDocument format et al. More information can be found at <a href="http://de.openoffice.org/linuxtag2008/">http://de.openoffice.org/linuxtag2008/</a></content> - <author> - <name>floeff</name> - <uri>http://ooomarketing.blogspot.com/</uri> - </author> - <source> - <title type="html">OpenOffice.org Marketing Blog</title> - <link rel="self" href="http://ooomarketing.blogspot.com/feeds/posts/default"/> - <id>tag:blogger.com,1999:blog-4887643299605448632</id> - <updated>2008-04-01T17:00:47+00:00</updated> - </source> - </entry> - </feed> File [changed]: index.html Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/index.html?r1=1.300&r2=1.301 Delta lines: +24 -16 --------------------- --- index.html 2008-04-07 05:00:34+0000 1.300 +++ index.html 2008-04-07 11:00:55+0000 1.301 @@ -34,8 +34,31 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: April 07, 2008 05:00 AM GMT</em></p> +<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: April 07, 2008 11:00 AM GMT</em></p> +<h2>April 07, 2008</h2> +<h3> +<a href="http://standardsandfreedom.net"; title="Moved by Freedom - Powered by Standards » OOo Postings"> +Charles Schulz</a> : +<a href="http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/";> +The ugliness of it all</a> +</h3> +<p> +<p>I shall not complain that much about what happened with OOXML. In fact, the act of standardizing OOXML has not really brought any significant advantages to OOXML. ODF is an ISO standard and so is OOXML. That’s what I call a draw, and Microsoft has been battling hard for a bloody draw, as in the end, <a href="http://www.ft.com/cms/s/0/c9743360-01a8-11dd-a323-000077b07658.html?nclick_check=1";>the word has spread and everybody now knows about the insane amount of pressures Microsoft has applied to the ISO, the IEC, the ITTF and the national standards bodies</a>. But what will be the outcome of all this? Let me outline the following steps in Microsoft’s strategy in regard of standardization. This can be described as a pincer movement.</p> +<p> First, Microsoft will try to kill ODF. They can try to do this at two levels: at the level of the OASIS ODF TC, and at the level of the next iteration of ODF, ODF 1.2 (due sometimes this Fall and later to be brought on to the ISO). You can rest assured that Microsoft will exert pressures on the OASIS ODF committees either by attempting to stuff it, or by pressuring players such as Novell, Patrick Durusau, or even Sun Microsystems. One of them is a puppet of Microsoft, bound by heavy investment of Microsoft disguised as a legal and business partnership agreement (Novell), <a href="http://www.robweir.com/blog/2008/03/contra-durusau-part-1.html";>another one made an odd trip not that far from Redmond</a> and came back with a completely new view on OOXML and ODF (P. Durusau), while another one has a strong legal settlement with Microsoft and may not afford to lose it for obvious business reasons (Sun). </p> +<p> Another way for Microsoft to attack ODF would be to oppose the standardization of ODF 1.2. They will use the same tactics they had with OOXML, but in the opposite direction. It will be funny to watch how the ISO and the national standards bodies will switch all of a sudden to a demanding stance on ODF 1.2, <span class="Apple-style-span">which will only be an iteration of an existing ISO standard. </span>I am afraid we will witness such a shocking twist in the standardization bodies’ attitude. Romania, for instance, might completely change its happy-go-merry stance it had on OOXML (Approve without comments, twice) to an eagle-eye, unforgiving and watchdoggish scowl of ODF (Disapprove with… interesting comments). Heck, they might even use their former “laxist” attitude they had with OOXML as an excuse to block ODF, those masters of cynicism. </p> +<p> But all this is just one wing of  the pincer movement I am describing here. The other part of the strategy was however clear ever since the beginning. OOXML is the first chapter into an attempt by Microsoft to shove its own technologies to the ISO. Next in line will be XPS. If you don’t know what XPS is, <a href="http://www.microsoft.com/whdc/xps/default.mspx";>check it out from the source</a>. Yes, you got that right. PDF reloaded. Now with more patents, OOXML dependencies, and legal traps. What’s the advantage you ask? None. But the respectable industry players we saw in every national standards body (understand: Microsoft’s partners) will insist that it will offer them <span class="Apple-style-span">clarity </span>and a potential new source of <span class="Apple-style-span">revenue. </span>This time though Microsoft got really clever: They went where Adobe had forgotten to go for ages, to the printing industry. This time we will see HP really coming out with flowers for Redmond. In France , HP never joined the works of our committee but they got really supporting of OOXML all of a sudden, around Friday night and after somebody  (obviously being married to a woman of Italian descent with a nice hat, blue eyes, brown hair, ) had been given instructions to play nice with Microsoft. What you say, “<span class="Apple-style-span">is the French government bending to the will of Microsoft? Is it weaker than corporations?” </span>Depends whom you ask, who you can contact, and who you supported. Enough said. Back to XPS. </p> +<p>Well XPS is, believe or not, a standard in the making. And since it is being “<a href="http://www.ecma-international.org/memento/TC46.htm";>developed</a>” (ah, the game of mirrors, illusions and appearances) by the Ecma, it will be pushed through the very same Fast-Track process the Ecma has been lavishly endowed to use with OOXML. </p> +<p> Would you believe me if I wrote that I knew what’s in store after XPS? Let’s bet I know it. After OOXML shall come XPS. And once Microsoft will have locked the whole industry with its document formats, they will try to do the same with multimedia formats. Expect the future Windows Media formats, their proprietary video codecs to follow the same path. Their glue shall be Silverlight, which in turn rests on Windows Presentation Foundation and the .NET framework. The license shall be the famous OSP, effectively barring GPL implementations and leaving many other issues, such as the RAND mode applied on the covered technologies, in the shadows, but always as a critical factor to consider. Novell will follow, as usual, with incomplete and patent-riddled implementations that you will only be able to safely use with Novell products. </p> +<p> And then? Then,  as Shakespeare once magnificently wrote, then there shall be <span class="Apple-style-span">silence. </span>At last, silence to win, silence to dominate, silence to influence, silence to pressure, and silence to silence them all. <span class="Apple-tab-span"> </span> </p> +<p class="akst_link"><a href="http://standardsandfreedom.net/?p=59&akst_action=share-this"; title="E-mail this, post to del.icio.us, etc." id="akst_link_59" class="akst_share_link" rel="nofollow">Share This</a> +</p></p> +<p> +<em><a href="http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/";>by Charles at April 07, 2008 10:23 AM GMT</a></em> +</p> +<br /> +<hr /> +<br /> <h2>April 05, 2008</h2> <h3> <a href="http://lodahl.blogspot.com/search/label/OpenOffice.org"; title="Lodahl's blog"> @@ -458,21 +481,6 @@ <br /> <hr /> <br /> -<h2>March 26, 2008</h2> -<h3> -<a href="http://ooomarketing.blogspot.com/"; title="OpenOffice.org Marketing Blog"> -OOo Marketeers</a> : -<a href="http://ooomarketing.blogspot.com/2008/03/linuxtag-2008-with-openofficeorg-mini.html";> -LinuxTag 2008 with OpenOffice.org "mini conference"</a> -</h3> -<p> -At this year's LinuxTag, OpenOffice.org will host it's own "mini conference" (not to be confused with the official OpenOffice.org Conference). Several well-known project members will deliver speeches and lectures about OpenOffice.org, it's programmability, the ongoing migrations, the OpenDocument format et al. More information can be found at <a href="http://de.openoffice.org/linuxtag2008/";>http://de.openoffice.org/linuxtag2008/</a></p> -<p> -<em><a href="http://ooomarketing.blogspot.com/2008/03/linuxtag-2008-with-openofficeorg-mini.html";>by floeff at March 26, 2008 03:30 PM GMT</a></em> -</p> -<br /> -<hr /> -<br /> <a id="disclaimer" name="disclaimer"></a> <p><em>Disclaimer: all views expressed on this page are those of the individual contributors, and may not reflect the views of the File [changed]: opml.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/opml.xml?r1=1.300&r2=1.301 Delta lines: +1 -1 ------------------- --- opml.xml 2008-04-07 05:00:34+0000 1.300 +++ opml.xml 2008-04-07 11:00:56+0000 1.301 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Marketing Planet</title> - <dateModified>Mon, 07 Apr 2008 05:00:28 +0000</dateModified> + <dateModified>Mon, 07 Apr 2008 11:00:47 +0000</dateModified> <ownerName>Marketing Project</ownerName> <ownerEmail>[EMAIL PROTECTED]</ownerEmail> </head> File [changed]: rss10.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss10.xml?r1=1.197&r2=1.198 Delta lines: +15 -8 -------------------- --- rss10.xml 2008-04-06 17:01:11+0000 1.197 +++ rss10.xml 2008-04-07 11:00:56+0000 1.198 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-5185196905403355875" /> <rdf:li rdf:resource="http://www.solidoffice.com/archives/774"; /> <rdf:li rdf:resource="http://blogs.sun.com/dancer/entry/an_openoffice_letterhead_tutorial"; /> @@ -32,11 +33,24 @@ <rdf:li rdf:resource="tag:blogger.com,1999:blog-4887643299605448632.post-8748495239206685822" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-7115855525568860108" /> <rdf:li rdf:resource="http://www.mealldubh.org/index.php/2008/03/27/a-double-celebration/"; /> - <rdf:li rdf:resource="tag:blogger.com,1999:blog-4887643299605448632.post-4184165243450780018" /> </rdf:Seq> </items> </channel> +<item rdf:about="http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/";> + <title>Charles Schulz: The ugliness of it all</title> + <link>http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/</link> + <content:encoded><p>I shall not complain that much about what happened with OOXML. In fact, the act of standardizing OOXML has not really brought any significant advantages to OOXML. ODF is an ISO standard and so is OOXML. That&#8217;s what I call a draw, and Microsoft has been battling hard for a bloody draw, as in the end, <a href="http://www.ft.com/cms/s/0/c9743360-01a8-11dd-a323-000077b07658.html?nclick_check=1">the word has spread and everybody now knows about the insane amount of pressures Microsoft has applied to the ISO, the IEC, the ITTF and the national standards bodies</a>. But what will be the outcome of all this? Let me outline the following steps in Microsoft&#8217;s strategy in regard of standardization. This can be described as a pincer movement.</p> +<p> First, Microsoft will try to kill ODF. They can try to do this at two levels: at the level of the OASIS ODF TC, and at the level of the next iteration of ODF, ODF 1.2 (due sometimes this Fall and later to be brought on to the ISO). You can rest assured that Microsoft will exert pressures on the OASIS ODF committees either by attempting to stuff it, or by pressuring players such as Novell, Patrick Durusau, or even Sun Microsystems. One of them is a puppet of Microsoft, bound by heavy investment of Microsoft disguised as a legal and business partnership agreement (Novell), <a href="http://www.robweir.com/blog/2008/03/contra-durusau-part-1.html">another one made an odd trip not that far from Redmond</a> and came back with a completely new view on OOXML and ODF (P. Durusau), while another one has a strong legal settlement with Microsoft and may not afford to lose it for obvious business reasons (Sun). </p> +<p> Another way for Microsoft to attack ODF would be to oppose the standardization of ODF 1.2. They will use the same tactics they had with OOXML, but in the opposite direction. It will be funny to watch how the ISO and the national standards bodies will switch all of a sudden to a demanding stance on ODF 1.2, <span class="Apple-style-span">which will only be an iteration of an existing ISO standard. </span>I am afraid we will witness such a shocking twist in the standardization bodies&#8217; attitude. Romania, for instance, might completely change its happy-go-merry stance it had on OOXML (Approve without comments, twice) to an eagle-eye, unforgiving and watchdoggish scowl of ODF (Disapprove with&#8230; interesting comments). Heck, they might even use their former &#8220;laxist&#8221; attitude they had with OOXML as an excuse to block ODF, those masters of cynicism. </p> +<p> But all this is just one wing of  the pincer movement I am describing here. The other part of the strategy was however clear ever since the beginning. OOXML is the first chapter into an attempt by Microsoft to shove its own technologies to the ISO. Next in line will be XPS. If you don&#8217;t know what XPS is, <a href="http://www.microsoft.com/whdc/xps/default.mspx">check it out from the source</a>. Yes, you got that right. PDF reloaded. Now with more patents, OOXML dependencies, and legal traps. What&#8217;s the advantage you ask? None. But the respectable industry players we saw in every national standards body (understand: Microsoft&#8217;s partners) will insist that it will offer them <span class="Apple-style-span">clarity </span>and a potential new source of <span class="Apple-style-span">revenue. </span>This time though Microsoft got really clever: They went where Adobe had forgotten to go for ages, to the printing industry. This time we will see HP really coming out with flowers for Redmond. In France , HP never joined the works of our committee but they got really supporting of OOXML all of a sudden, around Friday night and after somebody  (obviously being married to a woman of Italian descent with a nice hat, blue eyes, brown hair, ) had been given instructions to play nice with Microsoft. What you say, &#8220;<span class="Apple-style-span">is the French government bending to the will of Microsoft? Is it weaker than corporations?&#8221; </span>Depends whom you ask, who you can contact, and who you supported. Enough said. Back to XPS. </p> +<p>Well XPS is, believe or not, a standard in the making. And since it is being &#8220;<a href="http://www.ecma-international.org/memento/TC46.htm">developed</a>&#8221; (ah, the game of mirrors, illusions and appearances) by the Ecma, it will be pushed through the very same Fast-Track process the Ecma has been lavishly endowed to use with OOXML. </p> +<p> Would you believe me if I wrote that I knew what&#8217;s in store after XPS? Let&#8217;s bet I know it. After OOXML shall come XPS. And once Microsoft will have locked the whole industry with its document formats, they will try to do the same with multimedia formats. Expect the future Windows Media formats, their proprietary video codecs to follow the same path. Their glue shall be Silverlight, which in turn rests on Windows Presentation Foundation and the .NET framework. The license shall be the famous OSP, effectively barring GPL implementations and leaving many other issues, such as the RAND mode applied on the covered technologies, in the shadows, but always as a critical factor to consider. Novell will follow, as usual, with incomplete and patent-riddled implementations that you will only be able to safely use with Novell products. </p> +<p> And then? Then,  as Shakespeare once magnificently wrote, then there shall be <span class="Apple-style-span">silence. </span>At last, silence to win, silence to dominate, silence to influence, silence to pressure, and silence to silence them all. <span class="Apple-tab-span"> </span> </p> +<p class="akst_link"><a href="http://standardsandfreedom.net/?p=59&amp;akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_59" class="akst_share_link" rel="nofollow">Share This</a> +</p></content:encoded> + <dc:date>2008-04-07T10:23:07+00:00</dc:date> +</item> <item rdf:about="tag:blogger.com,1999:blog-5198340507565233169.post-5185196905403355875"> <title>Leif Lodahl: MS answers to Master Thesis</title> <link>http://lodahl.blogspot.com/2008/04/ms-answers-to-master-thesis.html</link> @@ -306,12 +320,5 @@ <p>Finally, thanks to the many bloggers who have been desperate to announce the new release, but who have <a href="http://wiki.services.openoffice.org/wiki/PolicyMirrorLinking">complied with our request</a> not to leak the news prematurely for the greater good of the community.</p></content:encoded> <dc:date>2008-03-27T08:13:41+00:00</dc:date> </item> -<item rdf:about="tag:blogger.com,1999:blog-4887643299605448632.post-4184165243450780018"> - <title>OOo Marketeers: LinuxTag 2008 with OpenOffice.org "mini conference"</title> - <link>http://ooomarketing.blogspot.com/2008/03/linuxtag-2008-with-openofficeorg-mini.html</link> - <content:encoded>At this year's LinuxTag, OpenOffice.org will host it's own "mini conference" (not to be confused with the official OpenOffice.org Conference). Several well-known project members will deliver speeches and lectures about OpenOffice.org, it's programmability, the ongoing migrations, the OpenDocument format et al. More information can be found at <a href="http://de.openoffice.org/linuxtag2008/">http://de.openoffice.org/linuxtag2008/</a></content:encoded> - <dc:date>2008-03-26T15:30:32+00:00</dc:date> - <dc:creator>floeff</dc:creator> -</item> </rdf:RDF> File [changed]: rss20.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss20.xml?r1=1.197&r2=1.198 Delta lines: +15 -7 -------------------- --- rss20.xml 2008-04-06 17:01:11+0000 1.197 +++ rss20.xml 2008-04-07 11:00:56+0000 1.198 @@ -8,6 +8,21 @@ <description>Marketing Planet - http://marketing.openoffice.org/planet/</description> <item> + <title>Charles Schulz: The ugliness of it all</title> + <guid>http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/</guid> + <link>http://standardsandfreedom.net/index.php/2008/04/07/the-ugliness-of-it-all/</link> + <description><p>I shall not complain that much about what happened with OOXML. In fact, the act of standardizing OOXML has not really brought any significant advantages to OOXML. ODF is an ISO standard and so is OOXML. That&#8217;s what I call a draw, and Microsoft has been battling hard for a bloody draw, as in the end, <a href="http://www.ft.com/cms/s/0/c9743360-01a8-11dd-a323-000077b07658.html?nclick_check=1">the word has spread and everybody now knows about the insane amount of pressures Microsoft has applied to the ISO, the IEC, the ITTF and the national standards bodies</a>. But what will be the outcome of all this? Let me outline the following steps in Microsoft&#8217;s strategy in regard of standardization. This can be described as a pincer movement.</p> +<p> First, Microsoft will try to kill ODF. They can try to do this at two levels: at the level of the OASIS ODF TC, and at the level of the next iteration of ODF, ODF 1.2 (due sometimes this Fall and later to be brought on to the ISO). You can rest assured that Microsoft will exert pressures on the OASIS ODF committees either by attempting to stuff it, or by pressuring players such as Novell, Patrick Durusau, or even Sun Microsystems. One of them is a puppet of Microsoft, bound by heavy investment of Microsoft disguised as a legal and business partnership agreement (Novell), <a href="http://www.robweir.com/blog/2008/03/contra-durusau-part-1.html">another one made an odd trip not that far from Redmond</a> and came back with a completely new view on OOXML and ODF (P. Durusau), while another one has a strong legal settlement with Microsoft and may not afford to lose it for obvious business reasons (Sun). </p> +<p> Another way for Microsoft to attack ODF would be to oppose the standardization of ODF 1.2. They will use the same tactics they had with OOXML, but in the opposite direction. It will be funny to watch how the ISO and the national standards bodies will switch all of a sudden to a demanding stance on ODF 1.2, <span class="Apple-style-span">which will only be an iteration of an existing ISO standard. </span>I am afraid we will witness such a shocking twist in the standardization bodies&#8217; attitude. Romania, for instance, might completely change its happy-go-merry stance it had on OOXML (Approve without comments, twice) to an eagle-eye, unforgiving and watchdoggish scowl of ODF (Disapprove with&#8230; interesting comments). Heck, they might even use their former &#8220;laxist&#8221; attitude they had with OOXML as an excuse to block ODF, those masters of cynicism. </p> +<p> But all this is just one wing of  the pincer movement I am describing here. The other part of the strategy was however clear ever since the beginning. OOXML is the first chapter into an attempt by Microsoft to shove its own technologies to the ISO. Next in line will be XPS. If you don&#8217;t know what XPS is, <a href="http://www.microsoft.com/whdc/xps/default.mspx">check it out from the source</a>. Yes, you got that right. PDF reloaded. Now with more patents, OOXML dependencies, and legal traps. What&#8217;s the advantage you ask? None. But the respectable industry players we saw in every national standards body (understand: Microsoft&#8217;s partners) will insist that it will offer them <span class="Apple-style-span">clarity </span>and a potential new source of <span class="Apple-style-span">revenue. </span>This time though Microsoft got really clever: They went where Adobe had forgotten to go for ages, to the printing industry. This time we will see HP really coming out with flowers for Redmond. In France , HP never joined the works of our committee but they got really supporting of OOXML all of a sudden, around Friday night and after somebody  (obviously being married to a woman of Italian descent with a nice hat, blue eyes, brown hair, ) had been given instructions to play nice with Microsoft. What you say, &#8220;<span class="Apple-style-span">is the French government bending to the will of Microsoft? Is it weaker than corporations?&#8221; </span>Depends whom you ask, who you can contact, and who you supported. Enough said. Back to XPS. </p> +<p>Well XPS is, believe or not, a standard in the making. And since it is being &#8220;<a href="http://www.ecma-international.org/memento/TC46.htm">developed</a>&#8221; (ah, the game of mirrors, illusions and appearances) by the Ecma, it will be pushed through the very same Fast-Track process the Ecma has been lavishly endowed to use with OOXML. </p> +<p> Would you believe me if I wrote that I knew what&#8217;s in store after XPS? Let&#8217;s bet I know it. After OOXML shall come XPS. And once Microsoft will have locked the whole industry with its document formats, they will try to do the same with multimedia formats. Expect the future Windows Media formats, their proprietary video codecs to follow the same path. Their glue shall be Silverlight, which in turn rests on Windows Presentation Foundation and the .NET framework. The license shall be the famous OSP, effectively barring GPL implementations and leaving many other issues, such as the RAND mode applied on the covered technologies, in the shadows, but always as a critical factor to consider. Novell will follow, as usual, with incomplete and patent-riddled implementations that you will only be able to safely use with Novell products. </p> +<p> And then? Then,  as Shakespeare once magnificently wrote, then there shall be <span class="Apple-style-span">silence. </span>At last, silence to win, silence to dominate, silence to influence, silence to pressure, and silence to silence them all. <span class="Apple-tab-span"> </span> </p> +<p class="akst_link"><a href="http://standardsandfreedom.net/?p=59&amp;akst_action=share-this" title="E-mail this, post to del.icio.us, etc." id="akst_link_59" class="akst_share_link" rel="nofollow">Share This</a> +</p></description> + <pubDate>Mon, 07 Apr 2008 10:23:07 +0000</pubDate> +</item> +<item> <title>Leif Lodahl: MS answers to Master Thesis</title> <guid>tag:blogger.com,1999:blog-5198340507565233169.post-5185196905403355875</guid> <link>http://lodahl.blogspot.com/2008/04/ms-answers-to-master-thesis.html</link> @@ -289,13 +304,6 @@ <p>Finally, thanks to the many bloggers who have been desperate to announce the new release, but who have <a href="http://wiki.services.openoffice.org/wiki/PolicyMirrorLinking">complied with our request</a> not to leak the news prematurely for the greater good of the community.</p></description> <pubDate>Thu, 27 Mar 2008 08:13:41 +0000</pubDate> </item> -<item> - <title>OOo Marketeers: LinuxTag 2008 with OpenOffice.org "mini conference"</title> - <guid>tag:blogger.com,1999:blog-4887643299605448632.post-4184165243450780018</guid> - <link>http://ooomarketing.blogspot.com/2008/03/linuxtag-2008-with-openofficeorg-mini.html</link> - <description>At this year's LinuxTag, OpenOffice.org will host it's own "mini conference" (not to be confused with the official OpenOffice.org Conference). Several well-known project members will deliver speeches and lectures about OpenOffice.org, it's programmability, the ongoing migrations, the OpenDocument format et al. More information can be found at <a href="http://de.openoffice.org/linuxtag2008/">http://de.openoffice.org/linuxtag2008/</a></description> - <pubDate>Wed, 26 Mar 2008 15:30:32 +0000</pubDate> -</item> </channel> </rss> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
