Mozilla joins the W3C DAP – WebAPI progress

When we originally introduced our work on WebAPI, we got a number of questions where a particular question was the most frequently asked. Now, four months later, we wanted to follow up with what has been happening since.

The question people asked was about the relation between Mozilla WebAPI and W3C DAP, what our stance on DAP is and if we were just creating another standards body. From the get go, we declared our commitment and intent to contribute to existing standards.

Mozilla has a long history working with W3C and continues to be a member in several W3C working groups. However, at the time we had concerns about some of the work happening in DAP. Since then, DAP has focused their efforts on technologies appropriate for implementation in web browsers and so we’ve have decided that it’s worth joining that working group. Our developers Jonas Sicking and Mounir Lamouri have now joined DAP to ease the collaboration and contribution.

What this means in practice is that we test and develop things, and when we feel that it is ready, or even suitable, to become a standard and continue to evolve, we submit it to W3C. Like most companies, we need to evaluate, examine and prototype different ideas all the time, but what might be different about us is that our process is open to the world to see, ask about and also contribute to.

Even before this, we have submitted the Battery API and the Vibration API to DAP, which are both pretty far along in standardization. We look forward to continue to do so with APIs as they get mature enough.

If you are interested in following or taking part of the work with our different APIs, feel more than welcome to follow any of these channels:

Please also ask any questions you might have in the comments here, and we’ll do our best to reply to them.

View full post on Mozilla Hacks – the Web developer blog

Tagged on: , , ,

4 thoughts on “Mozilla joins the W3C DAP – WebAPI progress

  1. David Bruant

    A lot of people are suggesting the switch from Gecko to WebKit. Instead of just saying “switch!” to Mozilla (which doesn’t lead anywhere closer to the goal you would like to see achieved), what about taking some time to analysis the problem such a transition would be. What about starting the work (and blog about your findings)?

    If you (and other people who want to see the transition happening) can prove that it can lead to a better browser at a reasonable cost, your findings would certainly get heard by Mozilla.

  2. Robert Nyman

    First, this blog post, and the WebAPI initative, is about bringing powerful API’s to all web browsers and devices out there, and it’s not something Gecko-specific.

    Second, Erunno linked to a long and good explanation. Basically, Mozilla believes in competition and giving people options. These options has lead to a fast and successful development for web browsers, something that everyone gains from.

    Back when Internet Explorer was the web browser out there with 95% market share, it would have been easy to cave and just develop for that one. But we didn’t, and brought another perspective to the table.

    And when WebKit started being developed, you could have easily argued for them to contribute to Gecko instead. But we didn’t, since more options are good, spurs competition and leads to better results.

Leave a Reply