One major benefit if a configuration system is the ashurance to use the correct profiles.
A recently closed flaw in the ICC spec was a missing identification tag inside the profile. While profiles may have varaying names and descriptions, the now in the ICC standard included md5 checksum approach fits well in the demand of easily and relyable distinguish between various profiles.
The plan is to check or possibly recalculate the md5 sum and modify the profile in the header accordingly. This makes sense especially for older profiles. This feature makes of course only sense of the file access is resonably quick. A hash table may help here.
An other toppic is the correlation of device and program settings during image production and the selection of the correct profile for the needed conversions. The profile should allways fit to the tool chain used. My suggestion is here to embedd these settings in a easy recoverable way into the profile. A special ascii tag could be used therefor.
External libraries like sane or cups should tell Oyranos theyre settings and query for a suitable profile. In the case of a not finding a fitting profile the external library may ask for an alternative list of settings. With selecting the desired settings the profile can be selected. The goal herein is to give the user the freedom of choice and the security regarding quality.
More proposals and ideas can be found on http://www.behrmann.name in the Oyranos section.
Generated on Sat Jun 16 21:05:41 2007 for Oyranos by
1.5.1