On March 13, OpenSocial apps were released to the public in beta on MySpace. This marks the first public launch among OpenSocial-compatible social networks. Why and how did this happen, even though the OpenSocial specification hasn't been fully finalized yet?

OpenSocial Container standard fragmentation – Implementing OpenSocial Containers | Google グループ

To summarize the thread:

MySpace's OpenSocial API appears to use proprietary specifications for both its JavaScript extensions and RESTful APIs. At this rate, won't we be forced to conform to the specifications created by the world's largest SNS rather than the standard specification?

In response to this question, a debate ensued comparing the situation to issues with Office XML standards or browser standards. However, as of the 21st, a developer from hi5 replied as follows:

We are aware of this issue and want to resolve it. A meeting has been scheduled for next week, and since this meeting was proposed by MySpace, they must be aware of the issue too. We also have proposals prepared for template systems, presence, etc.

It appears that the OpenSocial specification isn't just being driven by Google; developers from major US social networks other than Facebook—such as hi5, MySpace, and Ning—are gathering, bringing proposals to the table, and deciding on the specs together.

I was under the impression that things had settled down to some extent with version 0.7 (at least for the JavaScript API), but it seems there are still many changes ahead.

Perhaps it would be a good idea for Japanese developers (myself included) to start actively submitting proposals as well.