<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Adobe on ManuSoft</title><link>https://www.manusoft.com/tags/adobe/</link><description>Recent content in Adobe on ManuSoft</description><generator>Hugo</generator><language>en-us</language><copyright>1991–2026</copyright><lastBuildDate>Sun, 10 Dec 2006 16:42:00 +0000</lastBuildDate><atom:link href="https://www.manusoft.com/tags/adobe/index.xml" rel="self" type="application/rss+xml"/><item><title>The secret world of file formats</title><link>https://www.manusoft.com/archive/blog/secret-world-of-file-formats/</link><pubDate>Sun, 10 Dec 2006 16:42:00 +0000</pubDate><guid>https://www.manusoft.com/archive/blog/secret-world-of-file-formats/</guid><description>&lt;p&gt;No matter the communication protocol used to transmit it, most information gets packaged into a file format for consumption. File formats are like virtual checkpoints along the information superhighway, and we would do well to pay attention to who is manning the gates.&lt;br /&gt;&lt;br /&gt;We&amp;rsquo;ve heard a lot of noise lately about the need for &amp;ldquo;open&amp;rdquo; file formats, but documenting a file format is not the same thing as relinquishing control of the format. The key consideration is who decides when and how the file format changes. This is a dirty little secret about file formats that you are not supposed to know. By controlling when and how a file format changes, an organization can maintain a mindshare monopoly over consumers of its file format &amp;ndash; even when the format is &amp;ldquo;open&amp;rdquo;.&lt;br /&gt;&lt;br /&gt;It may be that the relative anarchy of the internet has given us a false sense of security. We happily use &amp;ldquo;open&amp;rdquo; formats like PDF, DWF, DXF, HTM, and others with relatively little concern about who controls them, but all of those formats (HTM perhaps to a lesser degree) are controlled by corporations whose allegiance is first and foremost to their shareholders. For example, PDF is &amp;ldquo;open&amp;rdquo;, but did you know that third party developers need a digital ID signed by &lt;a href="http://www.adobe.com/"&gt;Adobe&lt;/a&gt; in order to create forms-enabled PDF files that can be opened in the free Acrobat Reader?&lt;br /&gt;&lt;br /&gt;In April of 2006, Autodesk filed a &lt;a href="http://tarr.uspto.gov/servlet/tarr?regser=serial&amp;amp;entry=78852798"&gt;trademark application for the word &amp;ldquo;DWG&amp;rdquo;&lt;/a&gt; when used to refer to DWG files. This may seem benign on the surface, but if successful it will give Autodesk more legal leverage in &amp;ldquo;defending&amp;rdquo; the file format. A few weeks ago, &lt;a href="http://www.autodesk.com/"&gt;Autodesk&lt;/a&gt; filed a &lt;a href="http://www.cadcourt.com/Docket/206cv01637AutodeskvODA.aspx"&gt;trademark infringement lawsuit&lt;/a&gt; against the &lt;a href="http://www.opendesign.com/"&gt;Open Design Alliance&lt;/a&gt; claiming that the ODA infringed their &amp;ldquo;AUTODESK&amp;rdquo; trademark by embedding the mark inside DWG files created with its DWGdirect libraries.&lt;br /&gt;&lt;br /&gt;Much has been written by the pundits about the pros and cons of the ODA lawsuit, and the &lt;a href="http://www.eff.org/"&gt;Electronic Frontier Foundation&lt;/a&gt; predictably suggests that Autodesk is &lt;a href="http://www.eff.org/deeplinks/archives/005038.php"&gt;using trademark claims to stymie interoperability&lt;/a&gt;, but the bottom line is that the contention centers around a file format &amp;ndash; a file format that Autodesk considers valuable enough to wage war over.&lt;/p&gt;</description></item></channel></rss>