Khronos Public Bugzilla
Bug 678 - Distinguish between community-approved and Khronos-ratified WebGL extensions
Distinguish between community-approved and Khronos-ratified WebGL extensions
Status: NEW
Product: WebGL
Classification: Unclassified
Component: Registry
unspecified
All All
: P3 normal
: ---
Assigned To: 3dweb Working Group email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-17 16:48 PDT by Kenneth Russell
Modified: 2012-07-19 19:21 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Russell 2012-07-17 16:48:10 PDT
Currently the WebGL extension registry uses the term "official" extension specification to describe extensions which the community has agreed upon. However, this term is conflated with the notion of Khronos ratified extensions. We need to distinguish between the two, minimally, and ideally probably send the existing official extensions through the Khronos ratification process (which I've been assured should be painless).
Comment 1 kosmo.zb 2012-07-17 17:12:43 PDT
Other Khronos extension registries appear to use the Status section of extension specifications for this purpose.

I propose using an optional <ratification date="YYYY/MM/DD" /> tag under <extension> for this purpose. Processors may then generate and insert ratification statements into the Status section as they wish. For instance, when the ratification tag is absent, Status could state "Ratification by Khronos Blah Blah Blah is pending." &c.

Are there any practical ramifications of Khronos ratification/non-ratification vs. community approval?
Comment 2 Kenneth Russell 2012-07-19 19:21:49 PDT
(In reply to comment #1)
> Other Khronos extension registries appear to use the Status section of
> extension specifications for this purpose.
> 
> I propose using an optional <ratification date="YYYY/MM/DD" /> tag under
> <extension> for this purpose. Processors may then generate and insert
> ratification statements into the Status section as they wish. For instance,
> when the ratification tag is absent, Status could state "Ratification by
> Khronos Blah Blah Blah is pending." &c.

Thanks for the suggestion. In order to be very clear about the status I've currently implemented this in the registry by adding a new "ratified" tag alongside "extension" and "draft". It would be really good to add the ratification date, though. If you would have time to contribute a patch which would support it (even though we don't have any ratified extensions yet) I'd appreciate it.

> Are there any practical ramifications of Khronos ratification/non-ratification
> vs. community approval?

I'm not 100% sure how much information is publicly available about what exactly is entailed by ratification by the Khronos board of promoters. Let's suffice it to say that there are benefits to the implementers of the specifications.