No subject

backends collect device and driver settings informations on request.
Oyranos can then embedd these informations into a intermediate profile 
during calibration. The intermediate profile shall be feed together with 
the typical CGATS measurement data to the profiler, which can include the 
intermediate profile tags into the final device profile.

The scheme would involve following steps:
* colour patch I/O (e.g. scan of a IT8)
* parallel collection of device and driver informations
* obtaining of device or measurement values
* profiling with the device and measured values
* adding of device and driver informations to final ICC profile

For individual profiles it could be as simple as that.

For vendor profiles the documentation of the appropriate Oyranos driver 
backend should be read to see how the matching and ranking works there.
With that information it should be possible to support wide ranges of 
devices and conditions in much fewer profiles. To obtain platform 
independence a driver vendor had to use the algorithms with other CMSes.

As soon as a acceptable scheme is found I want to present the results to 
ICC's CMS vendors to get there feedback. There is interesst in this toppic 
too.

Yiannis started with some nice schemes about the application, Sane,
Oyranos relations. So I came around sketching about profiling for people 
who like graphics:
http://www.oyranos.org/wiki/index.php?title=Device_Settings#Profiling


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