[Openicc] XICC specification draft

[Kai-Uwe Behrmann]

Am 28.06.05, 21:16 -0600 schrieb Chris Murphy:

> > About the general option I would agree. Nethertheless tagging with the
> > display profile instead of declaring the image is prematched is
> > dangerous.
> > 
> 
> The net effect is the same, if the system and the xserver get the profile from
> the same location, you are assured that they are the same and that a null
> transform will occur. But I think an explicit "off" switch is preferable
> because it's very clear, whereas the null transform approach involves
> redundancy and an explanation of the concept.

I will support in Oyranos several ways to fetch profiles. It is currently 
not clear if these ways work all the same. For instance it is possible to 
ask the X server about the _ICC_PROFILE atom. On a local machine it may be 
supported to request the display profile name and obtain it from file. A 
application is free to decide which way to use. 
As long as we dont want to let applications set transformations in a CMS 
itself, targeting null transforms is not predictable.

An explicit flag will avoid ambiguitys, resulting in a more simple, 
relyable and perhaps quickier system.


> 1. Explicit request to opt out, device dependent, prematched.
> 2. "For free" sRGB assumed source, display profile is destination, display
> compensation. Application developer needs to do nothing different than they
> are today.
> 3. Explicit request for something other than sRGB as source, by tagging RGB
> data submitted display.

Simply agreed.

regards
Kai-Uwe Behrmann
                                + development for color management 
                                + imaging / panoramas
                                + email: ku.b at gmx.de
                                + http://www.behrmann.name