Thoughts on the New WebGL Open API Standard
Posted by Brian Kelly on 7 April 2011
A Brief Introduction to WebGL
The TechCrunch article provides a summary of WebGL:
As a cross-platform API within the context of HTML5, it brings 3D graphics to the Web without using plug-ins. WebGL is managed and developed by The Khronos Group, a non-profit consortium of companies like Google, Apple, Intel, Mozilla, and more, dedicated to creating open standard APIs through which to display digital interactive media — across all platforms and devices.
Over the past decade or so that W3C’s approach to the development of open standards has focussed on the development of declarative markup languages based on XML such as SMIL and SVG. But here’s another approach which is based on providing open APIs with buy-in from browser vendors and other IT companies. Might WebGL have an impact in the development of interactive e-learning and research applications, I wonder?
But Is WebGL Really Open?
Investigations into the potential of WebGL for development work in higher and further education should consider its openness and its likely sustainability. Although is has been developed and maintained by a non-profit consortium it is questionable whether an API maintained by an industry consortium should be regarded as an open standard according to a definition of an open standard which the UK Government is currently attempting to define. As described in a recent post the UK Government’s first condition for an open standards is that it is “result[s] from and are maintained through an open, independent process“. A industry consortium, even if non-profit making, surely cannot be considered independent; if this was the case Microsoft could set up a similar consortium responsible for the maintainance of their formats and code base which they could then claim to be an open standard.
But such considerations are really only relevant for those who feel there is a simple binary divide between open standards and proprietary approaches. In my view there is a complex spectrum of openness and for now I would feel that WebGL is worth considering for development work – and the fact that WebGL is not supported by Microsoft should be regarded as an interesting challenge for developers but not necessarily a reason for discounting it.
Observing WebGL’s Development
It should be noted that there is an entry for WebGL in Wikipedia and, as is often the case, the article provides a useful brief summary of the standard:
I must admit I hadn’t realised that statistics for revisions of Wikipedia articles are available. The statistics for the WebGL article reveal that there have been 192 revisions from 104 users. It is also possible to view details for those who have edited the article and to discover how many users are watching the article.
What have I learnt from observing the information about the WebGL Wikipedia article, as well as the information provided in the WebGL Wikipedia article itself?
The chart of the number of edits over time shows that there is a steady growth in the number of edits, which suggests that the article is continually being revised. The main contributors to the article include those involved in development in computer games which may suggest that the priority for future developments may be in this area. However the article itself lists Google Body as an early application of WebGL which perhaps suggests that WebGL could have a role to play in the development of teaching and learning applications.
Are there any examples of early use of WebGL within the higher education sector, I wonder? I would be interested in hearing about examples and, perhaps more importantly, hearing about experiences of those involved in WebGL development work.
In addition I’d be interested in comments on observation of use and changes in Wikipedia articles as a means of providing early indications of new standards which may be of interest to developers. Is this an approach which could be used more widely?