[Openicc] Re: LINUX ... Color policies / ICC-workflow-group

[Jan-Peter Homann]

Hello Ann, hello list

I appreciate very much, that leading ICC-members take activly part of 
this list, that we all together can learn from the view of others.

I think, the idea of metadata, which describes the colorhistory of an 
image can be useful in some special cases. But what we need more urgent 
are descriptions of colorworkflows incl. testdata, that we can see if 
the tested application or the tested profiles behave like the 
description og the colorworkflow.

The W3C wrote the SVG-standard and als gave a testsuite to the 
community, that developers can test their applications  accordings the 
W3C specifications.

If the ICC is defining workflows, it should also offer a testsuite 
according the defined workflows.

The testsuite should adress the functionality of applications and the 
evaluation of profiles seperatly.

The use of recommended workingspaces would be very helpful for building 
testsuites:

- applications can be tested, if they are able to transform imported 
files to the workingspace and do proper transformation from the 
workingspace to the monitor and to the printer.

- the quality of complete colortransformtions:
(workingspace-profile->gamumappting-output-profile->linearization) can 
be tested, if the application is tested before.

If these tests are OK, we can test how the application handles differnt 
placed filetype with embedded profiles and rendering intents, or if the 
application is able to handle metadata for the colorhistory of images.

--

Do the ICC plans to offer testsuites for applications and profiles 
according their wokflow recommendations under a free licence, that also 
endusers or opensource developers can use this testsuites ?

greetings
:-) Jan-Peter



almccart at lexmark.com schrieb:
> 
> Greetings List,
> 
> I have recently joined - and am quite interested in the current 
> conversation.
> As some of you may know, the ICC has a Workflow WG and we are currently
> working on writing down system level requirements for color management
> -  intentionally not of current implementations but rather "what it 
> should be."
> 
> Jan-Peter's comments point out some of the issues with color management
> in systems today.
> 
>  >Actually, we have four possibilities to apply and use profiles
>  >during the printing process:
>  >
>  >- colormanagement in the application
>  >- colormanagement with an ICC to CSA/CRD conversion during Ripping
>  >- colormanagement as CUPS-Filter on rasterized data
>  >- colormanagement as part of the printer-driver e.g. gutenprint
> 
> Also in earlier posts I saw discussions about metadata carried with the 
> content file, profiles
> carried with or referenced from the content file, etc.
> 
> I have been thinking about this for some time - and the color space 
> dependent policy approach
> does not appear robust to handle the variety of workflows and use cases 
> that do exist and need
> to exist - even though I agree that such policy approaches are all we 
> have to work with today.  
> Unfortunately, the caveat of  "if they know what they want, and if they 
> organize
> their workflow properly" is large enough to drive a truck through. The 
> current failures and
> unexpected results with mixed color type object documents are often due 
> to incompatible 'policy'
> assumptions at various points in workflows and distributed image paths.

-- 
--

homann colormanagement ------ fon/fax +49 30 611 075 18
Jan-Peter Homann ------------- mobile +49 171 54 70 358
Kastanienallee 71 ------- http://www.colormanagement.de
10435 Berlin --------- mailto:homann at colormanagement.de