I have test results that show that there is much work to be done.
The most likely path forward at this point is to get representatives from browser vendors into a room and go through these results and make recommendations. This likely will happen in the spring, and in the SF Bay Area. With that in place, I can work with authors of libraries in popular programming languages to produce web-compatible versions. This work will take the form of bug reports, patches, or — when required — authoring new libraries.
Status by venue:
At the WHATWG, I’m limited only by my own ability to do the work required. My biggest complaint remains that that the barrier to entry to participate is too high. This. however, is something entirely under my control to fix for the specifications I’m working on. I’m hopeful that leading by example will cause others in the WHATWG to do likewise.
I’ve had some success, but virtually all of this is attributable to GitHub, not WebPlatform. At the moment, technical issues prevent me from updating the spec there. These issues started on December 24th and were promptly reported. If this continues, I’ll push the webspecs develop branch to a whatwg develop branch and migrate the issues.
There has been no demonstrable progress in the WebApps WG. The TAG seems generally supportive. I briefed the AB, but nothing has come of that. Same is true for the process CG. I’m willing to try proposing a new working group. Failing this, I believe that I have all the evidence I need to convince the W3C Director that normative references to the Living Standard are the only viable alternative. As Sherlock Holmes was known to say: when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
I’ve met with Area Directors. I’ve participated on the apps-discuss mailing list. With the help of Larry Masinter, I’ve produced and published a problem statement. Sadly, this seems like a clear case of you can lead a horse to water, but you can’t make it drink. Should this change, I have until February 5th to propose a BOF.
More details and links are available in the README.