[Openicc] meta data in test chart

[Kai-Uwe Behrmann]

Am 21.01.11, 05:00 +0100 schrieb edmund ronald:
> On Fri, Jan 21, 2011 at 4:44 AM, Chris Murphy <lists at colorremedies.com> wrote:
>> I don't thoroughly understand all of the components and how they interact with each other. But from a end-user advocate perspective, the very generic way I'd like it to work is that everything related to the print condition is a single sharable file. It would contain: the state of all drive dialog options such as resolution, screening, color mode, inkset, etc, any externally referenced calibration file, any externally referenced ICC profile. All in one shareable package.
>
> I agree that at the very least one should be able as a user to
> retrieve such a file, so as to have the "recipe" which can then be
> handed out.

Again, the meta tag in ICC allowes for all colour related options inside 
the ICC profile. The settings need to be serialised to single line 
key/value pairs. Thats a technical detail and is solvable on a technical 
level. (We have done the abstraction as a OpenICC project for Oyranos 
two years ago.) Once the colour settings are embeded into the ICC profile, 
the ICC profile itself is the single file containing all data. It can be 
shared, installed and deployed without further action once the CMS 
supports parsing of the tag and can map to device classes.

That scheme can be used as well for monitors, scanners and cameras.

> There are obvious reasons why this amalgamated model is very nice.

Agreed.

> There are unobvious reasons why things won't get done this way
> internally (eg. print settings contain paper feed settings, but paper
> feed settings  have little to do with ink-curves, so we have a tuple)

I think we have to do a cut here. IMO it would be straight forward to just 
care about settings being colour related. After all that sounds to me like
what you want with the calibration "recipe".

kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org