W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

Re: [csswg-drafts] [css-color] predefined spaces

From: Chris Lilley via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Jul 2016 12:17:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-232337609-1468412219-sysbot+gh@w3.org>
So this could be done two ways. 

One is to provide the same info we do for dci-p3 and rec.2020 - a 
table of red, green, blue and white chromaticities and the transfer 
curve. That allows conversion to Lab and thus to any other colorspace,
 for colors in gamut. It does not define handling for colors outside 
of gamut (and I think we should define it, including black point 
compensation, equivalent to the "relative colorimetric" rendering 
intent so in-gamut colors are faithfully preserved and we can have 
interop.

The other is to provide an ICC profile and require browsers to act as 
if this has been specified with an @profile with a local descriptor 
(rather than a src). That gives you whatever rendering intent (or 
intents, for those few profiles that have more than one) the profile 
specifies and gives you whatever handling of out of gamut colors that 
intent has. (for perceptual intent, it will also affect in-gamut 
colors). And it requires deciding on ICC v.2 or ICC v.4.

I think my preference would be to do the table like dci-pr3 and 
rec.2020 have. Dino, an ICC profile would still be very helpful to me 
because I can look inside it and see what it says.  Also agree about 
AdobeRGB (once we get assurance from Adobe about the trademark issue) 
and ProPhoto, both for the digital SLR crowd.

-- 
GitHub Notification of comment by svgeesus
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/292#issuecomment-232337609 
using your GitHub account
Received on Wednesday, 13 July 2016 12:17:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:00 UTC