On 17.11.2012 01:36, Dale wrote:
>> *Sigh*, no I'm not confusing this. I've already written CMMs, if you
>> care. The PCS does not have rendering choices in the same sense that the
>> R^3 does not have vector choices. It is the CMM that can implement
>> various rendering intents.
>>
>
> a profile can be populated with 4 intents, perceptual relative to a
> print, maintain saturation, colorimetric and absolute colorimetric
>
> the PCS is instantiated to represent the intents and conversion spaces
> chosen or specified
>
No, it's not, for the last time! An *ICC profile* includes a rendering
intent. It *also* defines a profile connection space, but the profile
connection space has no rendering intent.
How often do I need to explain you that the PCS is just a common
coordinate space to express colors both of the input and the display (or
output) device?
The ICC profile contains enough information to convert from the device
color space to the PCS and back. It defines the type of the PCS, it also
defines the rendering intent which, again, defines the peculiarities in
how to interpret the coordinate transformation (or how or where to find
it). But the PCS is nothing but the coordinate frame in which colors are
expressed. It doesn't have an intent. If coordinate transformations
could be done in infinite precision, and if we wouldn't care about
practical implementation limits, the PCS would not even matter. We could
pick XYZ for everything and express coordinates always in XYZ.
The CMM is the piece of software that implements the coordinate
transformation to and from the PCS. It implements the rendering, and by
that also defines how to realize the rendering intent - it has some freedom.
But why the heck don't you just download the specs from
color.org and
read them yourselves?