Here's a piece of the language from that sane standard that addresses
image formats and mentioned that "the interface has been defined carefully
to allow extending it in the future".
3.2 Image Data Format
Arguably the most important aspect of an image acquisition system
is how images are represented. The SANE approach is to define a
simple yet powerful representation that is sufficient for vast
majority of applications and devices. While the representation is
simple, the interface has been defined carefully to allow extending
it in the future without breaking backwards compatibility. Thus,
it will be possible to accommodate future applications or devices
that were not anticipated at the time this standard was created.
Although it doesn't specifically say so, it seems to me that one
mechanism put in place to allow extension is the frametype. And
there certainly is no mention of the magical all encompassing mime
frametype arriving to save the day.
With the frametypes _JFIF, _JBIG, _G31D, _G32D, and _G42D what we are
trying to do is "accommodate future applications or devices that were
not anticipated at the time this standard was created" in the most
straighforward and painless manner.
Why is the process of getting there so painful?
Tom Martone
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com