Request OpenGL SC and Vulkan

Keep OpenGL SC and Vulkan separate.
Make an Vulkan SC for Vulkan instead of merging OpenGL SC and Vulkan.
OpenGL and Vulkan are very different.
Since OpenGL and Vulkan will be developed separately it’s also necessary to develop the SC profiles separately.
Thus having both an OpenGL SC and Vulkan SC for Safety Critical Markets would make a natural fit and work optimally for the market.

Thank You for your feedback. We will take it into consideration.

There are no current plans on merging OpenGL SC and Vulkan. OpenGL SC will remain a safety critical version of OpenGL ES. If and when there are enough Khronos members interested in developing a safety critical version of Vulkan, it will most likely be developed based on Vulkan and not OpenGL SC or OpenGL ES.

My personal opinion is that it is too early to develop a safety critical version of Vulkan at this time. Vulkan needs time to mature in the market before it is worthwhile to develop a safety critical version of it. Safety critical specifications need to be stable for many years, and right now Vulkan is growing both in install base and in functionality. Perhaps in a a year or two it will be time to look at developing a safety critical version of Vulkan.