Norbert Nopper

> @HuaweiNopper It probably would make sense to have the same basic test models for both extensions. I can try to create a `float16` version (although this is usually not...

> > > @HuaweiNopper It probably would make sense to have the same basic test models for both extensions. I can try to create a `float16` version (although this is...

> > It is more about creating the examples. Furthermore, in most cases the data can be passed 1:1 to the GPU. > > I understand that this is just...

In general, I like splitting up the extension. However, to avoid future fragmentation and/or duplication, I recommend to define it more generic, as defining a color encoding is required not...

As this has been discussed. There are folks, who want to use RAW image data. E.g. this paper is describing it: https://aryan-garg.github.io/hdrsplat/

> Hi, I work for Autodesk and am serving as the chief architect on the [OpenColorIO](https://opencolorio.org/) project, which is a color management system that is used in applications from Autodesk,...

@doug-walker We consider to use the values from here also in the base extension: https://github.com/AcademySoftwareFoundation/ColorInterop/blob/main/Recommendations/01_TextureAssetColorSpaces/TextureAssetColorSpaces.md#summary-table--overview-of-the-recommendations Reviewed in a smaller group on Tuesday and then presented to 3D Formats on Wednesday.

Okay, thanks I got it.

I do not know, if finally the naming will be changed in the glTF extensions. At minimum, there should be the mapping possible. As soon as we proceed on this...

One problem I do see is, that the list is not yet complete and all the `_display` ones are not listed yet.