Reference:
http://wiki.opensocial.org/index.php?title=Clarify_Separation_of_Gadgets_and_OpenSocial_in_the_specs
This is the first step in the process, I'd like to ensure there is
some preliminary support behind this, and no -1's, because the next
steps gets a bit harder. I decided to address the Gadgets API
Specification first, and thought of 2 different methods and would like
to get people's opinion on them.
Option 1:
http://codereview.appspot.com/144070
Make the changes in the Gadget API Specification, clearly highlighting
the OpenSocial specifics.
Option 2:
http://codereview.appspot.com/144071
Remove most references to OpenSocial, and all the OpenSocial specifics
from the Gadget API Specification, and create a new section in the
OpenSocial Specification to describe the extensions to the Gadget API
Specification.
I have not done any modification to the Gadget XSD, since that is
currently being changed by another proposal, and I don't want to
create needless conflicts.
Step 2 will require a bit of discussion should there be no strong
-1's. The issue is what to do with the word "opensocial" when it is
used for non-OpenSocial Gadget functionality, such as:
opensocial_i18n, opensocial_proxied_content, and all the references in
the templating, pipelining specs.