OpenRAW

The RAW Flaw, Solution Proposal C: Define and ratify a standard OpenRAW specification and enable it with Open Source software.

I applaud, and support, a means to archive RAW image data. However, getting manufacturers to publish their proprietary formats is an incomplete solution, not to mention an up-hill battle. In the final analysis, the purpose of publishing any proprietary RAW format would be to allow conversion of one RAW file format to another, from a "closed" to an "open" format or from an unsupported (old) to a supported (newer) format. Such a conversion might undertaken simpley for archival purposes, or just to convert a file from a "dead" format to one that can be read by PhotoShop, or some other image processing software.

The act of publishing a proprietary format, in and of itself, is not an archive solution. Without translation software, unsupported and documented proprietary formats are as worthless as their undocumented siblings.

A true archive solution is one where software exists that converts proprietary formats into a suitable "standard" archival format. Ideally, such a format would be independently developed, would be a "true" standard, blessed by the likes of the IEEE or ANSI, it would be well documented and it would be mostly static but with the ability to change over time as new features are required. Additionally, and most importantly, the specification would be given life through Open Source and freely-available software.

Given these needs, I believe the OpenRAW group should begin a second, two-pronged initiative: it should define, and seek ratification for, a truly open and standard OpenRAW specification and it should support the development of Open Source software that would host manufacturer-written plugins that translate proprietary formats to and from the OpenRAW standard format.

By standardizing and openly publishing the OpenRAW format and then encouraging manufacturers to write software plugins that translate their data to the open format, manufacturers can protect the creative and innovative Intellectual Property (IP) in their proprietary formats. Translation plugins would be loaded into the Open Source OpenRAW translation software suite on-the-fly (PhotoShop, Eclipse and numerous other applications do this already), allowing users to convert proprietary formats to the OpenRAW format and back. Manufacturers wouldn't need to divulge their unique IP, just read their proprietary data and write it to a new format and back again.

Support should be included in the host translation application to encrypt the plugins to prevent reverse-engineering data formats by reverse engineering a plugin. Additionally, the RAW Flaw really only comes into play when a format is no longer supported. Current formats are supported by proprietary processors, as well as by Adobe's, ULead's, Jasc's, ACD's (and others') software offerings. So, manufacturers should be encouraged to write translation plugins for their unsupported formats, and for formats nearing end-of-life. This would address the bulk of the problems created by unsupported RAW formats.

There are undoubtedly a number of challenges in this approach, as well as numerous technical hurdles to overcome. However, this approach meets the needs of the OpenRAW community (conversion of unsupported formats to a readable format) and it allows the manufacturers to protect their IP. The alternative (getting manufacturers to divulge what they perceive to be valuable trade secrets) will meet stern resistance and, I believe, will ultimately fail. A compromise that embraces the needs of both sides of the problem would be more likely to lead to a tractable solution.

Just my $.02-worth.

-=< tom >=-
Tom Funk
Germantown, MD.