- From: Thomas Mansencal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Oct 2018 20:42:55 +0000
- To: public-svg-issues@w3.org
I think what @sobotka is trying to explain is that using the *LinearRGB* term does not give you any information about the intrinsics of the colourspace itself, implying that you have to make assumptions about the underlying encoding of the RGB values. A few years ago, it was probably relatively safe (albeit still bad) to assume it is sRGB encoded, but today with the advent of HDR and Wide Colour Gamuts, DCI-P3 or BT.2020 are very common. To be unambiguous, RGB colourspaces must be specified with the three components @sobotka enumerated [above](https://github.com/w3c/svgwg/issues/366#issuecomment-429889474). Now on the linearity topic, RGB colourspaces are intrinsically linear, the first RGB colourspace, CIE RGB derived by Wright (1928) and Guild (1931) has no defined colour component transfer function (CCTF), i.e., OEFT and EOTF. We use them mainly for bandwidth/storage optimizations in accordance with the non-linear response of the Human Visual System (HVS) to brightness. However, in a perfect world neglecting commercial performance and expenses, one might conceive colour imaging systems based on high-quality floating point representations where non-linear encoding would not be necessarily required. -- GitHub Notification of comment by KelSolaar Please view or discuss this issue at https://github.com/w3c/svgwg/issues/366#issuecomment-430005913 using your GitHub account
Received on Monday, 15 October 2018 20:43:04 UTC