Proposal for 1.0 - Clarify Separation of Gadgets and OpenSocial in the specs (part 1)

1 view
Skip to first unread message

Jon

unread,
Oct 30, 2009, 7:33:24 PM10/30/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
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.

goosemanjack

unread,
Nov 2, 2009, 1:52:30 PM11/2/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
My preference is for Option 2 (extracting Gadget extensions for
OpenSocial into the OpenSocial spec). It more clearly identifies
OpenSocial as an extension built on top of Gadgets and eases the job
of implementers by keeping all opensocial-specific features in the
OpenSocial spec.
--
clc



On Oct 30, 3:33 pm, Jon <jon.weyga...@gmail.com> wrote:
> Reference:http://wiki.opensocial.org/index.php?title=Clarify_Separation_of_Gadg...

Louis Ryan

unread,
Nov 4, 2009, 12:43:21 PM11/4/09
to opensocial-an...@googlegroups.com
Proposal needs to address osapi. While not currently part of the spec you can easily imagine protocol driven services like makeRequest being migrated into osapi e.g. osapi.http.get(...), osapi.http.post(...) etc.

--

You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.



Reply all
Reply to author
Forward
0 new messages