There are also different types of open-standards to consider with. Android libraries, the Java programming language, the PDF specification, and so forth are largely defined by a single body. On the other hand, they are also open. (At least in the case of Java and PDF, where there are multiple implementations and support on a broad range of devices. I do not know how open Google is to reimplementations of the Android libraries.)

There are also various reasons why committee based open standards progress slowly. The failure to reach an agreement and even outright sabotage are big in the picture. On the other hand, you don't want standards progressing too quickly because a big point of standardization is interoperability across both vendors and time. For example: it is unlikely that KF8 will ever operate on first and second generation Kindle. Amazon doesn't care, because they want to sell new products. However, when interoperability enters the picture you do have to care and stable standards over long periods of time is the easiest way to do it.