I like it!
Could the next draft update the HTML portion to work that way? That'd
help make it work more like one specification, and address a few of the
biggest problems I perceive in that part of the spec.
> This means that the various
> definitions of the API are sure to be *consistent*, but if the master XML
> is wrong, they all are wrong.
As shown by the exception non-declarations ... I thought I detected the
actions of some automated tool! :-)
- Dave