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

Re: [Public WebGL] Changing extension spec boilerplate



On Wed, Jun 20, 2012 at 6:44 PM, Mark Callow <callow_mark@hicorp.co.jp> wrote:
> I'm working on an extension spec proposal. I need to change some of the
> boilerplate generated by xslt as the html is generated from the xml. For
> example <additions> results in "Additions to the OpenGL ES 2.0
> Specification." I need it to say "Additions to the WebGL Specification." How
> do I do this?

After
webgl/extensions$ grep -R additions *

Edited like

Index: extension.xsl
===================================================================
--- extension.xsl	(revision 18279)
+++ extension.xsl	(working copy)
@@ -128,7 +128,7 @@
       </xsl:if>

       <xsl:if test="additions">
-        <h2 class="no-toc">Additions to Chapters of the OpenGL ES 2.0
Specification</h2>
+        <h2 class="no-toc">Additions to the WebGL Specification</h2>
         <xsl:copy-of select="additions/node()" />
       </xsl:if>

Index: template/extension.xml
===================================================================
--- template/extension.xml	(revision 18279)
+++ template/extension.xml	(working copy)
@@ -116,7 +116,7 @@
   <security></security>
   <ipstatus></ipstatus>
   <newtypes></newtypes>
-  <additions></additions> <!-- Additions to Chapters of the OpenGL ES
2.0 Specifications -->
+  <additions></additions> <!-- Additions to the WebGL Specification -->
   <errors></errors>
   <newstate></newstate>
   <newimplstate></newimplstate> <!-- New Implementation-Dependent State -->

> Also is there a DTD for the spec. template that I could point my XML editor
> at so it knows what elements are available?

No DTD currently exists.

Many elements simply contain XHTML5 (implemented with xsl:copy-of in
extensions/extension.xsl as above).

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).

What XML editor do you use? Does it understand any other XML schema languages?

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?

Warm wishes,

David

> Regards
>
> -Mark

-----------------------------------------------------------
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
-----------------------------------------------------------