[Openicc] monitor profiling

[edmund ronald]

The open source issue is marginal to most companies' business, and
many of them do not offer open source support not because of active
opposition to the idea but mainly because they don't have the time to
"waste" to think it over.

Maybe politely indicating to Xrite that not fulfilling a customer
request for support offers an niche and entry point for a competitor
who does offer the requested support would provide some (slight)
economic motivation for them, superior to the 1% of business that they
would actually gain from the Linux community.

I think a stronger argument is that Xrite is dominant in the color
measurement business, and that a standardisation of interfaces to
instruments always consolidates the advantage of the player who
defines the interface.

In practice, I think one only gets open source support in companies
where there is an internal open-source advocate - maybe some senior
scientist at Xrite would wish to act as such an advocate ?

Surely, Xrite are seeing the practical benefits of open source, as the
most solid color-managed platform is the Mac, and all the compilers
and most of the Mac OS base layers and utilities are open-source.

IBM is doing very well out of open source, thank you :)

Edmund


>
> As a side note the SDK information for the EyeOne library can be found on the
> net if you dig around enough.  Having that information would be comparable to
> having " reverse-engineered" the SDK APIs.  The problem is that the
> information is useless if X-Rite will not release the interface library for
> the platforms we use.  And so far at least they have not even though they
> have had linux versions of the library internally since at least 2004.  So we
> have exactly the same issue with X-Rite.
>