Google Groups Home
Help | Sign in
Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes .html
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  7 messages - Collapse all
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Dan Peterson  
View profile
 More options May 9, 9:29 pm
From: "Dan Peterson" <dpeter...@google.com>
Date: Fri, 9 May 2008 18:29:09 -0700
Local: Fri, May 9 2008 9:29 pm
Subject: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

As per below, please use this thread to discuss potential improvements to
the release notes:
http://opensocial-and-gadgets-spec.googlegroups.com/web/1-OpenSocial_...

-Dan


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Paul Lindner  
View profile
 More options May 14, 5:41 am
From: Paul Lindner <lind...@inuus.com>
Date: Wed, 14 May 2008 02:41:31 -0700
Local: Wed, May 14 2008 5:41 am
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

* Didn't we define a filter for networkPresence?  (maybe I'm not
  remembering...)

* refreshInterval is also availble on makeRequest() calls

--
Paul Lindner        ||||| | | | |  |  |  |   |   |
lind...@inuus.com

  application_pgp-signature_part
1K Download

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Peterson  
View profile
 More options May 22, 1:10 pm
From: "Dan Peterson" <dpeter...@google.com>
Date: Thu, 22 May 2008 10:10:02 -0700
Local: Thurs, May 22 2008 1:10 pm
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

On Wed, May 14, 2008 at 2:41 AM, Paul Lindner <lind...@inuus.com> wrote:
> * Didn't we define a filter for networkPresence?  (maybe I'm not
>  remembering...)

It isn't actually a filter, but it does hang off of the person field.

> * refreshInterval is also availble on makeRequest() calls

Good catch!

Thanks,
-Dan


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Arne Roomann-Kurrik (Google)  
View profile
 More options May 23, 9:11 pm
From: "Arne Roomann-Kurrik (Google)" <api.kur...@google.com>
Date: Fri, 23 May 2008 18:11:32 -0700 (PDT)
Local: Fri, May 23 2008 9:11 pm
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html
Looking over the spec, I've noticed a couple places that will make 0.7
gadgets incompatible with 0.8:

  * The removal of VIEWER_FRIENDS and OWNER_FRIENDS in favor of the
IdSpec object.
  * The change from opensocial.Activity.MediaItem =>
opensocial.MediaItem
  * LOOKING_FOR went from string => opensocial.Enum.LookingFor
  * newFetchActivitiesRequest returns a Collection<Activity> instead
of an object

Can we highlight these changes in this document, to make porting a bit
more straightforward?

Thanks,
~Arne

On May 22, 10:10 am, "Dan Peterson" <dpeter...@google.com> wrote:


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Peterson  
View profile
 More options May 23, 9:38 pm
From: "Dan Peterson" <dpeter...@google.com>
Date: Fri, 23 May 2008 18:38:23 -0700
Local: Fri, May 23 2008 9:38 pm
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

Good suggestions.

Thanks,
-Dan

On Fri, May 23, 2008 at 6:11 PM, Arne Roomann-Kurrik (Google) <


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
David Glazer  
View profile
 More options May 26, 10:23 pm
From: David Glazer <dgla...@google.com>
Date: Mon, 26 May 2008 19:23:18 -0700
Local: Mon, May 26 2008 10:23 pm
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

In addition to highlighting in the spec, do we have a policy on backwards
compatibility?  In spec-speak, what is the right version of "If the gadget
asks for opensocial-0.8, containers { MUST NOT | MAY | SHOULD | MUST }
 accept the old syntax also." ?
(I'm assuming that gadgets that ask for opensocial-0.7 will keep working as
long as containers choose to keep supporting it, and that reference
implementations like Shindig will make that easy; the question is about
gadgets that choose to step forward to 0.8.)

  - dG


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
John Hjelmstad  
View profile
 More options May 27, 6:44 pm
From: John Hjelmstad <fa...@google.com>
Date: Tue, 27 May 2008 15:44:27 -0700
Local: Tues, May 27 2008 6:44 pm
Subject: Re: Detailed feedback thread: 1-OpenSocial_0_8_Release_Notes.html

We don't have this right now, but we should carefully consider adding it.

It's incumbent on each version of the spec to define what it means to be
compliant with the version of OpenSocial defined therein. We don't have a
Backward Compatibility section, so a site can be OpenSocial 0.8 compliant
and happily refuse to support 0.7 gadgets if it so chooses.

Each iteration will have to grapple with the trade-off between code
maintenance/complexity and wide support for existing gadgets. For cases
where the new version is a superset of the previous N versions, the burden
is small and N-version backward compatibility makes sense. If we were to
fundamentally rewrite how OpenSocial works, the tax might be large enough to
discourage adoption.

All pretty obvious, but I wanted to put it out there. That brings us to: do
people feel strongly enough about 0.8 backward compatibility with
{0.7,0.6,0.5} to warrant adding this section for strict compliance? Or, is
it worth adding a SHOULD-style clause for encouragement?

--John

On Mon, May 26, 2008 at 7:23 PM, David Glazer <dgla...@google.com> wrote:

In addition to highlighting in the spec, do we have a policy on backwards
compatibility?  In spec-speak, what is the right version of "If the gadget
asks for opensocial-0.8, containers { MUST NOT | MAY | SHOULD | MUST }
 accept the old syntax also." ?
(I'm assuming that gadgets that ask for opensocial-0.7 will keep working as
long as containers choose to keep supporting it, and that reference
implementations like Shindig will make that easy; the question is about
gadgets that choose to step forward to 0.8.)

  - dG

On Fri, May 23, 2008 at 6:38 PM, Dan Peterson <dpeter...@google.com> wrote:

Good suggestions.

Thanks,
-Dan

On Fri, May 23, 2008 at 6:11 PM, Arne Roomann-Kurrik (Google) <

api.kur...@google.com> wrote:

Looking over the spec, I've noticed a couple places that will make 0.7
gadgets incompatible with 0.8:

 * The removal of VIEWER_FRIENDS and OWNER_FRIENDS in favor of the
IdSpec object.
 * The change from opensocial.Activity.MediaItem =>
opensocial.MediaItem
 * LOOKING_FOR went from string => opensocial.Enum.LookingFor
 * newFetchActivitiesRequest returns a Collection<Activity> instead
of an object

Can we highlight these changes in this document, to make porting a bit
more straightforward?

Thanks,
~Arne

On May 22, 10:10 am, "Dan Peterson" <dpeter...@google.com> wrote: