CMM support (Was: Re: [Openicc] google SoC starts)

Bob Friesenhahn bfriesen at simple.dallas.tx.us
Fri Mar 16 12:10:12 PDT 2007


On Fri, 16 Mar 2007, Ken Kameda wrote:

> What are your thoughts on the architecture of the CMM abstraction APIs?
> Would the CMM abstraction APIs be used entirely within Scribus, with
> plug-ins used as wrappers around existing CMMs (like littlecms), or
> would the goal be for CMMs to directly adopt and export the common CMM
> APIs themselves?

The best approach is for someone to develop interface header files and 
an API specification under a non-encumbering license (e.g. MIT style) 
and then each CMM vendor provides a module satisfying that interface. 
The module could be an adaptor to a CMM, or it could be an inherent 
part of the CMM.  The application using the module does not care which 
CMM vendor provided the module, or about the module's usage license. 
The CMM module would be independently supplied by the end user (or OS 
distribution) from the using application.  Some modules may be GPL 
licensed, some may be MIT licensed, and some may be commercially 
licensed for $$$.

Bob
======================================
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/



More information about the openicc mailing list