| |||||||||||||
Mozilla launches WebAPIMozilla launches WebAPIPosted Aug 23, 2011 15:41 UTC (Tue) by landley (guest, #6789)Parent article: Mozilla launches WebAPI
(Log in to post comments)
standards Posted Aug 23, 2011 16:03 UTC (Tue) by tialaramex (subscriber, #21167) [Link]
Although this cartoon will seem very familiar to anyone who has worked on standardisation, it is not the inevitable outcome of every such effort.
ISO 9660 CDs are everywhere, and only when its inherent size limits began to become frustrating did a newer standard take some mindshare.
USB Mass Storage has been a tremendous success. If you introduced a new USB storage device that requires vendor drivers today you wouldn't stand a chance.
ISO 10646 also, has essentially no rivals (there are several anti-Unicode efforts but none of them has any traction)
And of course I wouldn't be writing this here, and you wouldn't be reading it, without at least TCP/IP and HTTP.
Mozilla launches WebAPI Posted Aug 23, 2011 16:50 UTC (Tue) by lkundrak (subscriber, #43452) [Link]
What's WebAPI's competition?
Mozilla launches WebAPI Posted Aug 24, 2011 14:27 UTC (Wed) by KaiRo (subscriber, #1987) [Link]
Actually, the phonegap people are participating in Mozilla's WebAPI discussions, and Mozilla is participating in various W3C standards discussions surrounding those APIs (some of those mentioned in the WebAPI wiki page are actually already part of W3C work, some still need to be developed).
Making web apps that use open web standards able to do everything native apps on mobile devices can do nowadays is a relatively young field and there are not a lot of standards there yet - Mozilla and other stakeholders need to work together to create good standards (that follow open web principles as well as privacy etc.) for that, and also make preliminary implementations to see how they fare (that's why B2G/"Boot to Gecko" and WebAPI teams work closely together there at Mozilla).
Mozilla launches WebAPI Posted Aug 24, 2011 13:01 UTC (Wed) by KaiRo (subscriber, #1987) [Link]
You seem to not have read the announcements and comments of the people involved. This is to build on and extend existing W3C standards where possible and create new ones that "will be submitted to the W3C" in draft form and standardized there where none exist yet.
No "14 competing standards" anywhere there. And surely you agree that any competition to OOXML is also wrongdoing, right? If not, there may even be the case where the *one* existing similar standard is not the right one to go with in the end. But there's still a difference between one and fourteen even in this case, and most of the areas the WebAPI team tackles are about working with existing standards or creating entirely new web standards (there are not a lot of *web* standards for such things at all).
|
|||||||||||||