Thank you very much for your reply.
...I was hoping for a way that does not break the build of existing extension spec's. How about if I add a <webgl-additions> node by cloning the <additions> node?After webgl/extensions$ grep -R additions * Edited like ...
I know. I've been following it. Speaking of extension.xml I get an instance of the following error for each extension processed by xsltproc each time I run make:... extensions/template/extension.xml describes in comments the source generating <http://www.khronos.org/registry/webgl/extensions/template/> using the major features of the system (notably missing the recently added cross-specification references).
XMLMind. It understands DTD's W3D XML Schema and RELAX NG Schema.What XML editor do you use? Does it understand any other XML schema languages?
It extends the WebGL API. It also extends state and GLSL but those parts of will be coming from an existing OES extension. Once I have the proposal in reasonable shape I'll post it to this list for discussion.I am interested to know more about your use case. Which components (e.g. API, state, GLSL) of the standard does your proposal extend? Does the extension introduce any new namespaces or reference any external namespaces?