<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>OpenDocument's feed | Diigo Group</title>
    <link>http://groups.diigo.com/opendocument/bookmark/tag/marbux+interoperability</link>
    <description>Bookmarks from OpenDocument tagged by marbux+interoperability</description>
    <pubDate>Wed, 09 Apr 2008 17:22:53 -0000</pubDate>
    <item>
      <title>OOXML and ODF: The next step | [odf-discuss] Marbux Responds!</title>
      <link>http://lists.opendocumentfellowship.com/pipermail/odf-discuss/2008-April/007308.html</link>
      <description>&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;Outstanding analysis and research by the legendary marbux &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;The issue we were discussing -- and what I believe the ODEF conference was
very much concerned with -- was whether ODF plus  vendor-specific extensions
will be classified as conformant ODF. The market requirement is for
&quot;Exchange Formats&quot; and document-level interoperability.

I could repose my question as whether ODF v. 1.2 will &quot;clearly and
unambiguously specify interoperability requirements essential to achieve the
interoperability,&quot; as required by JTC 1 Directives. As you noted in an
earlier post in this thread, you can't do interoperability if you use vendor
extensions.


&amp;gt;&lt;i&gt; I see a standard as providing a shared vocabulary for buyers and sellers
&lt;/i&gt;&amp;gt;&lt;i&gt; to express their requirements.
&lt;/i&gt;

You are in error. This is a matter controlled by law rather than by personal
opinion. Standards are all about the substitutability of goods, weights, and
measures. A standard specifies all characteristics of a product, weight, or
measure in mandatory terms so there is uniformity. Standards are the
antithesis of product differentiation. Their very purpose is to eliminate
product differentiation.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/interop&quot;&gt;interop&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/interoperability&quot;&gt;interoperability&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/iso&quot;&gt;iso&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/marbux&quot;&gt;marbux&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ooxml&quot;&gt;ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/opendocument-fellowship&quot;&gt;opendocument-fellowship&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 09 Apr 2008 17:22:53 -0000</pubDate>
    </item>
    <item>
      <title>Re: [office-metadata] Suggested Changes on the Metadata proposal</title>
      <link>http://lists.oasis-open.org/archives/office-metadata/200706/msg00072.html</link>
      <description>&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;Marbux is clearly at the top of his game here as he hammers the interoperability issue.   &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;span class=&quot;content&quot;&gt;&lt;img src=&quot;http://www.diigo.com/images/v2/float_note.gif&quot; /&gt;&lt;/span&gt;&lt;ul&gt;&lt;li&gt;Preserving metadata!  Preserving application specific information.  Preserving &quot;unknown&quot; information inside of a document &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;Unless we add conformance requirements for the preservation of metadata and processing instructions, the less featureful apps will never&amp;nbsp; be able to round-trip documents with the more featureful apps. Our language should require that. Personally, I believe that the software-as-an-end-point client-side office suites are dinosaurs at the end of their era. They are being finished off by a thousand cuts as users spend less and less time using them and more and more time using other apps, such as web apps. ODF either develops methods for interoperability among all apps or it will die along with the office suites. 
E.g., Microsoft knows this and is busily migrating its Office development budget across the Sharepoint/Exchange server hubs to the network. Meanwhile, this TC fiddles with preserving the 1995 software-as-an-endpoint vision.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/conformance-clause&quot;&gt;conformance-clause&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/interoperability&quot;&gt;interoperability&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/marbux&quot;&gt;marbux&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/metadata&quot;&gt;metadata&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Thu, 23 Aug 2007 21:04:54 -0000</pubDate>
    </item>
  </channel>
</rss>