- From: Henry Wilkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Dec 2022 05:59:20 +0000
- To: public-design-tokens-log@w3.org
Good point with the cylindrical models, obvious in hindsight! > I’m not familiar with use cases for an encoding value, as an ICC profile name or color space defines that information (with the exception of bit depth in RGB). With [normal maps](https://en.wikipedia.org/wiki/Normal_mapping) the texture is stored in RGB channels but the green channel either signifies +Y in OpenGL or -Y in DirectX. Artists authoring them (in this imaginary use case picking the value of part of a normal map which is actually stored in non-rgb channels to transfer that value between applications) must keep this in mind while creating their textures to ensure they are properly interpreted by the renderer. Therefore, it's potentially useful to specify both the colorspace (in this case interpret these values as data and forego any transformations) and the encoding format (how the green channel should be interpreted specifically). Maybe that's the _only_ situation where this would be helpful and it's niche enough to not bother including? > that sounds like a bad practice, but I don’t know that I would expect the spec to enforce these rules. It would be! And also I agree. -- GitHub Notification of comment by Shrinks99 Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/79#issuecomment-1333251835 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 December 2022 05:59:22 UTC