- From: Sam Weinig via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Oct 2021 16:05:10 +0000
- To: public-css-archive@w3.org
@smfr What do you think? We just shipped support for this, so it's unlikely it is used anywhere, but if anyone adopts now, they are going to have slightly broken content. My slight personal preference would be to keep it at D50, not only because we have shipped, but also because it happens to match what CoreGraphics calls `kCGColorSpaceGenericXYZ`, but I will admit that is arbitrary and mostly irrelevant. When I was trying to learn about colorspaces about a year and a bit ago, the notion that XYZ came in two flavors (actually, as infinite flavors I guess, or as many valid white points as there are, but for my purposes, two, D50 and D65) and that there was a conversion between that needed to happen, was quite confusing. I think what made it so confusing was that many places simply referred to it as the XYZ colorspace, and didn't mention which whitepoint they meant (usually they meant the one corresponding to the colorspace they were converting from). If more sources had been a little more explicit and said what they meant, XYZ(D50) or XYZ(D65) I think I would have been less confused. That all leads me to think that perhaps a better solution is to just be even more specific here and add the whitepoint to the name (or maybe do something crazy like make xyz into a function that takes a whitepoint (e.g. `color(xyz(d50) ...)`). -- GitHub Notification of comment by weinig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6722#issuecomment-940159567 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 October 2021 16:05:12 UTC