<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: OOXML — The Apple Headache</title>
	<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/</link>
	<description>Thoughts from up-north</description>
	<pubDate>Thu, 28 Aug 2008 01:49:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Martin</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6724</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 20 Feb 2008 20:09:45 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6724</guid>
		<description>Sorry for my late answer.

The files are available right here:

http://filer.bekkelund.net/dokumenter/neooffice.docx
http://filer.bekkelund.net/dokumenter/neooffice.odt
http://filer.bekkelund.net/dokumenter/neooffice.xlsx
http://filer.bekkelund.net/dokumenter/neooffice2.xlsx

And for what ODF concerns, it is not ODF that is up for ISO certification. ODF is already ISO certified and selected as the mandatory document standard for the public sector in Norway. Therefore, discussing ODF is uninteresting in this setting.</description>
		<content:encoded><![CDATA[<p>Sorry for my late answer.</p>
<p>The files are available right here:</p>
<p><a href="http://filer.bekkelund.net/dokumenter/neooffice.docx" rel="nofollow">http://filer.bekkelund.net/dokumenter/neooffice.docx</a><br />
<a href="http://filer.bekkelund.net/dokumenter/neooffice.odt" rel="nofollow">http://filer.bekkelund.net/dokumenter/neooffice.odt</a><br />
<a href="http://filer.bekkelund.net/dokumenter/neooffice.xlsx" rel="nofollow">http://filer.bekkelund.net/dokumenter/neooffice.xlsx</a><br />
<a href="http://filer.bekkelund.net/dokumenter/neooffice2.xlsx" rel="nofollow">http://filer.bekkelund.net/dokumenter/neooffice2.xlsx</a></p>
<p>And for what <acronym title="Open Document Format">ODF</acronym> concerns, it is not <acronym title="Open Document Format">ODF</acronym> that is up for <acronym title="International Organization for Standardization">ISO</acronym> certification. <acronym title="Open Document Format">ODF</acronym> is already <acronym title="International Organization for Standardization">ISO</acronym> certified and selected as the mandatory document standard for the public sector in Norway. Therefore, discussing <acronym title="Open Document Format">ODF</acronym> is uninteresting in this setting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hAl</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6717</link>
		<dc:creator>hAl</dc:creator>
		<pubDate>Sat, 16 Feb 2008 07:21:55 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6717</guid>
		<description>Could you enlighten us what kind of format your embedded picture file actually is ? 
Because it seems that a sample file I made that is very similar to your file is picked up fine by the iPhone of my friend.
Or better even give your readers a downloadable link to your sample files.</description>
		<content:encoded><![CDATA[<p>Could you enlighten us what kind of format your embedded picture file actually is ?<br />
Because it seems that a sample file I made that is very similar to your file is picked up fine by the iPhone of my friend.<br />
Or better even give your readers a downloadable link to your sample files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: orcmid</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6716</link>
		<dc:creator>orcmid</dc:creator>
		<pubDate>Fri, 15 Feb 2008 18:47:27 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6716</guid>
		<description>"First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not OOXML (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, DRM and SharePoint metadata. Even the paper handling does not conform with Ecma 376."

I think you have to be careful about these statements.  Both ODF and OOXML allow for use of binary content and for additional/alternative content in some cases.  The only specific example I have found so far was baseless, in that the behavior of Office 2007 was specifically allowed in ECMA-376.  (ODF also supports OLE enclosures, by the way.)

What needs to be looked at is how ECMA-376 provides for carrying of alternative content that may be useful in roundtripping back to older formats and how it is also easy to create conforming documents that make no reliance on such cases.  

With regard to the quality of implementations on Apple and the fact that Finder preview support has never been claimed, and other usability matters, I think your experimentation is very valuable, especially with regard to the important ability to round-trip with either one of OOXML or ODF among products that claim to support one or the other.</description>
		<content:encoded><![CDATA[<p>&#8220;First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not <acronym title="Office Open XML">OOXML</acronym> (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, <acronym title="Digital Rights Management">DRM</acronym> and SharePoint metadata. Even the paper handling does not conform with Ecma 376.&#8221;</p>
<p>I think you have to be careful about these statements.  Both <acronym title="Open Document Format">ODF</acronym> and <acronym title="Office Open XML">OOXML</acronym> allow for use of binary content and for additional/alternative content in some cases.  The only specific example I have found so far was baseless, in that the behavior of Office 2007 was specifically allowed in ECMA-376.  (<acronym title="Open Document Format">ODF</acronym> also supports OLE enclosures, by the way.)</p>
<p>What needs to be looked at is how ECMA-376 provides for carrying of alternative content that may be useful in roundtripping back to older formats and how it is also easy to create conforming documents that make no reliance on such cases.  </p>
<p>With regard to the quality of implementations on Apple and the fact that Finder preview support has never been claimed, and other usability matters, I think your experimentation is very valuable, especially with regard to the important ability to round-trip with either one of <acronym title="Office Open XML">OOXML</acronym> or <acronym title="Open Document Format">ODF</acronym> among products that claim to support one or the other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Open Sourcerer &#187; OOXML: Feeling the heat</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6715</link>
		<dc:creator>The Open Sourcerer &#187; OOXML: Feeling the heat</dc:creator>
		<pubDate>Fri, 15 Feb 2008 12:02:30 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6715</guid>
		<description>[...] And finally, and rather amusingly, Martin Bekkelund; has done some testing of Microsoft&#8217;s claims that OOXML works on several Apple products. Unfortunately it appears as thought they have been somewhat &#8220;economical with the truth&#8221; [Surely not! Microsoft?]&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] And finally, and rather amusingly, Martin Bekkelund; has done some testing of Microsoft&#8217;s claims that <acronym title="Office Open XML">OOXML</acronym> works on several Apple products. Unfortunately it appears as thought they have been somewhat &#8220;economical with the truth&#8221; [Surely not! Microsoft?]&#8230; [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boycott Novell &#187; Fighting for Its Survival, Microsoft Corrupts with OOXML</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6713</link>
		<dc:creator>Boycott Novell &#187; Fighting for Its Survival, Microsoft Corrupts with OOXML</dc:creator>
		<pubDate>Fri, 15 Feb 2008 02:13:21 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6713</guid>
		<description>[...] Microsoft is striding all over the place (even spamming YouTube) to give people the illusion that OOXML makes not just a representation of a single product from a single vendor. Actual users are not buying it (neither the argument nor Microsoft&#8217;s products) and it shows.  First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not OOXML (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, DRM and SharePoint metadata. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Microsoft is striding all over the place (even spamming YouTube) to give people the illusion that <acronym title="Office Open XML">OOXML</acronym> makes not just a representation of a single product from a single vendor. Actual users are not buying it (neither the argument nor Microsoft&#8217;s products) and it shows.  First of all, I will like to point out that the format of documents produced by Microsoft Office 2007 is not <acronym title="Office Open XML">OOXML</acronym> (Ecma 376). Microsoft Office 2007 documents contains, according to my sources, many elements not specified in Ecma 376, such as binary code, macros, OLE objects, ActiveX, <acronym title="Digital Rights Management">DRM</acronym> and SharePoint metadata. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6712</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:54:39 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6712</guid>
		<description>Having trouble with the comment system, Fredrik? ;-)

Anyway, we've had this discussion in my Norwegian weblog allready. As I said, at the moment it is not possible to use the so called implementations without having a license for Microsoft Office 2007 or 2008 for Mac. Probably.</description>
		<content:encoded><![CDATA[<p>Having trouble with the comment system, Fredrik? <img src='http://notebook.bekkelund.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Anyway, we&#8217;ve had this discussion in my Norwegian weblog allready. As I said, at the moment it is not possible to use the so called implementations without having a license for Microsoft Office 2007 or 2008 for Mac. Probably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik E. Nilsen</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6711</link>
		<dc:creator>Fredrik E. Nilsen</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:12:31 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6711</guid>
		<description>As you are well aware of, NeoOffice states that the support for OOXML is experimental. It's a bit hasty to draw the conclusions based on experimental support IMHO.</description>
		<content:encoded><![CDATA[<p>As you are well aware of, NeoOffice states that the support for <acronym title="Office Open XML">OOXML</acronym> is experimental. It&#8217;s a bit hasty to draw the conclusions based on experimental support IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik E. Nilsen</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6710</link>
		<dc:creator>Fredrik E. Nilsen</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:07:40 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6710</guid>
		<description>Type your comment here.</description>
		<content:encoded><![CDATA[<p>Type your comment here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6709</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:56:42 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6709</guid>
		<description>Are there anything in the 1.1.3 changelog that indicates improved OOXML support? I have not checked, but I doubt it.

As I say in my conclusion, it might be possible to open documents created with either Microsoft Office 2007 or Microsoft Office 2008 for Mac. However, this is rather irrelevant, as my point is to point out that the allegations of OOXML implementation in NeoOffice, iPhone and iWork '08 are wrong. If I have to own a license for Microsoft Office, the whole idea of vendor independence is useless.</description>
		<content:encoded><![CDATA[<p>Are there anything in the 1.1.3 changelog that indicates improved <acronym title="Office Open XML">OOXML</acronym> support? I have not checked, but I doubt it.</p>
<p>As I say in my conclusion, it might be possible to open documents created with either Microsoft Office 2007 or Microsoft Office 2008 for Mac. However, this is rather irrelevant, as my point is to point out that the allegations of <acronym title="Office Open XML">OOXML</acronym> implementation in NeoOffice, iPhone and iWork &#8216;08 are wrong. If I have to own a license for Microsoft Office, the whole idea of vendor independence is useless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Falk</title>
		<link>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6706</link>
		<dc:creator>Alexander Falk</dc:creator>
		<pubDate>Wed, 13 Feb 2008 22:18:14 +0000</pubDate>
		<guid>http://notebook.bekkelund.net/2008/02/13/ooxml-%e2%80%94-the-apple-headache/#comment-6706</guid>
		<description>I don't know what version of the software you are running on your iPhone, but since you are in Europe it is a safe bet to say that it is probably not yet 1.1.3, because when I send myself an e-mail with an OOXML attachment, such as a .DOCX file, I can indeed view that attachment on the iPhone without any problems. 
It works pretty much exactly as depicted in this YouTube video: http://youtube.com/watch?v=oNcAjS7LqKM</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what version of the software you are running on your iPhone, but since you are in Europe it is a safe bet to say that it is probably not yet 1.1.3, because when I send myself an e-mail with an <acronym title="Office Open XML">OOXML</acronym> attachment, such as a .DOCX file, I can indeed view that attachment on the iPhone without any problems.<br />
It works pretty much exactly as depicted in this YouTube video: <a href="http://youtube.com/watch?v=oNcAjS7LqKM" rel="nofollow">http://youtube.com/watch?v=oNcAjS7LqKM</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
