Re: [Public WebGL] WEBKIT_ extensions

[Mark Callow <callow_mark@hicorp.co.jp>]

    On 16/11/2011 04:15, Chris Marrin wrote:
    
> Additionally I don't think we should ever use prefixes like EXT (as in WEBGL_EXT_lose_context) for unratified extensions. EXT, ARB, OES, etc. should only ever be used to mimic the names of the corresponding Khronos extension.
>     
    I don't understand your objection to using EXT as a "prefix". EXT
    extensions are not Khonos ratified. It seems to me just as
    legitimate to use WEBGL_EXT for a WEBGL specific extension as for
    the WEBGL version of an existing EXT extension found in the Khronos
    registry. There should be no additional confusion caused. Both are
    unratified extensions whose spec's cannot be relied on as final.
> 4) The prefix should be prepended and never replace any part of the extension. So it should be WEBKIT_WEBGL_lose_context and not WEBKIT_lost_context.
>     
    In the Khronos extension naming principles the vendor / ext /
    working group "prefix" actually comes second in the extension string
    that an application searches for or passes to enable. The string
    starts with the API prefix. So the extension string in the above
    instance would be WEBGL_WEBKIT_lose_context and the extension name
    would be WEBKIT_lose_context.
    
    But I hope we can stick with WEBGL_EXT_lose_context.
    
    Regards
    
        -Mark