[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] extension candidates for khronos ratification from community approved

On Tue, Jan 6, 2015 at 5:10 AM, Florian Bösch <pyalot@gmail.com> wrote:
> On Tue, Jan 6, 2015 at 1:56 PM, Mark Callow <khronos@callow.im> wrote:
>> EXT extensions aren’t ratified by Khronos. They are simply multi-vendor
>> extensions.
> Objection irrelevant. This understanding of the extension process is derived
> from the ES-native registries, it has no bearing on the WebGL extension
> registry. Please consult https://www.khronos.org/registry/webgl/extensions/
> for the WebGL extension process.
> The EXT_ prefix (as well as any other prefix mirrored from an ES extension)
> does not have a specific meaning for the WebGL ratification process.
>> Khronos ratified extensions are those community approved extensions which
>> have been voted upon by the Khronos Board of Promoters
> Precedents for non OES extensions that've been WebGL Khronos Ratified:
> WEBGL_lose_context
> WEBGL_debug_renderer_info
> WEBGL_debug_shaders
> WEBGL_compressed_texture_s3tc
> WEBGL_depth_texture
> EXT_texture_filter_anisotropic
> WEBGL_draw_buffers
> ANGLE_instanced_arrays
> The status "community approved" was introduced so that WebGL extensions can
> be moved out of draft (where they would be vendor prefixed) in order to
> avoid extensions languishing in eternal draft hell until the Khronos board
> got around to ratify them.
> The goal of a community approved extension is to make it to Khronos ratified
> to complete the process.

The WebGL WG will consider submitting these extensions to the Khronos
Promoters for ratification. Thanks for providing availability


You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl