Kicking off OpenSocial 2.5.1!

[Matthew Marum]

We are kicking off development on OpenSocial 2.5.1!  As a minor release, the scope should be restricted to mostly specification bugs and clean-up.

If you have issues that you'd like see resolved in OpenSocial 2.5.1, please find or create an issue at http://code.google.com/p/opensocial-resources/ and respond with a link to it in this thread!

Development of OpenSocial 2.5.1 will occur in trunk.

http://opensocial-resources.googlecode.com/svn/spec/trunk/

Matt Marum

Spec Release Manager

[Laurent-Walter Goix]

Hello Matt, all,

herebelow are summarized the topics that would need be addressed for 2.5.1 for OMA references.

- update & delete REST paths: basically we promote the usage of the reference (id) to a single object in the URI path. for updates this means adding the Activity-Id or User-Id element in the REST-URI-Fragment itself, whilst obviously keeping the related object in the body. for deletions it means simply using that same approach instead of the body in DELETE messages (as some servers/proxies may have problems with handling http delete containing a body). This relates to the issues #1320 and #1327. We believe there is a need for consensus on this before proposing the related patch and as such i'd like to get feedback from the community on this.

- rest errors definition: i have submitted a patch a while ago (issue #1326) that wasn't applied yet. From the discussion (http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/b5e67eee48a5bb8a) it seemed however to be agreed. Is there any specific reason for not applying it?

thanks
walter

[Matthew Marum]

Hey Laurent, 

There's no hold up on my end other than time constraints.  For me, OpenSocial tasks have had to take a back seat to other priorities the last few months.  I'm going to start carving out Friday mornings as my "OpenSocial time", I hope to apply your patches/weigh in on issues between now and Friday morning.

There are other members of the community who have commit access as well who can apply patches, etc.  So hopefully if others have time to help close out 2.5.1, they can get more actively involved as well.

Matt

--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to opensocial-and-gadg...@googlegroups.com.

To post to this group, send email to opensocial-an...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/oZ6_FLLoTOwJ.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Matthew Marum]

"- update & delete REST paths: basically we promote the usage of the reference (id) to a single object in the URI path. for updates this means adding the Activity-Id or User-Id element in the REST-URI-Fragment itself, whilst obviously keeping the related object in the body. for deletions it means simply using that same approach instead of the body in DELETE messages (as some servers/proxies may have problems with handling http delete containing a body). This relates to the issues #1320 and #1327. We believe there is a need for consensus on this before proposing the related patch and as such i'd like to get feedback from the community on this."

I'm in support of including IDs in REST URIs wherever they have been overlooked.  AFAIC, all OpenSocial resources should uniquely addressable from a URL.  I've put comments into Issue-1320 and Issue-1327. 

I will apply the patch in Issue-1326 now.

Matt

On Monday, March 11, 2013 4:11:40 PM UTC-4, Matthew Marum wrote:

Hey Laurent, 

There's no hold up on my end other than time constraints.  For me, OpenSocial tasks have had to take a back seat to other priorities the last few months.  I'm going to start carving out Friday mornings as my "OpenSocial time", I hope to apply your patches/weigh in on issues between now and Friday morning.

There are other members of the community who have commit access as well who can apply patches, etc.  So hopefully if others have time to help close out 2.5.1, they can get more actively involved as well.

Matt

On Mon, Mar 11, 2013 at 6:31 AM, Laurent-Walter Goix <laurentwa...@gmail.com> wrote:

Hello Matt, all,

herebelow are summarized the topics that would need be addressed for 2.5.1 for OMA references.

- update & delete REST paths: basically we promote the usage of the reference (id) to a single object in the URI path. for updates this means adding the Activity-Id or User-Id element in the REST-URI-Fragment itself, whilst obviously keeping the related object in the body. for deletions it means simply using that same approach instead of the body in DELETE messages (as some servers/proxies may have problems with handling http delete containing a body). This relates to the issues #1320 and #1327. We believe there is a need for consensus on this before proposing the related patch and as such i'd like to get feedback from the community on this.

- rest errors definition: i have submitted a patch a while ago (issue #1326) that wasn't applied yet. From the discussion (http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/b5e67eee48a5bb8a) it seemed however to be agreed. Is there any specific reason for not applying it?

thanks
walter

Il giorno martedì 15 gennaio 2013 18:00:15 UTC+1, Matthew Marum ha scritto:

We are kicking off development on OpenSocial 2.5.1!  As a minor release, the scope should be restricted to mostly specification bugs and clean-up.

If you have issues that you'd like see resolved in OpenSocial 2.5.1, please find or create an issue at http://code.google.com/p/opensocial-resources/ and respond with a link to it in this thread!

Development of OpenSocial 2.5.1 will occur in trunk.

http://opensocial-resources.googlecode.com/svn/spec/trunk/

Matt Marum

Spec Release Manager

--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to opensocial-and-gadgets-spec+unsub...@googlegroups.com.

To post to this group, send email to opensocial-and-gadgets-spec@googlegroups.com.

[Laurent-Walter Goix]

thank you matt for your feedback. i'd be happy to hear from others (mark?) to get consensus. making both the body and id options may not be the best option in the long term, and may trigger interop issues unless servers support both...but it may be a sort of compromise...

walter

To post to this group, send email to opensocial-an...@googlegroups.com.

[Ryan Baxter]

All sounds good to me Walter

[Laurent-Walter Goix]

Thanks Ryan, all,

i just submitted 2 patches, one for issue-1320 (activitystreams), the other for 1327 (people) to allow including references to ids in the REST URIs.

at this stage i guess the only remaining issue is with the App-Id reference in the GET /activitystreams path: i am not sure how much this is used nowadays. if so, we may consider using the "@app" fixed placeholder in OMA specs or use it freely, once we get a better understanding from you of its potential value.

thanks
walter

[Matthew Marum]

Patches applied for Issues 1320 and 1327.

All OS 2.5.1 issues now have patches applied.  The specs changed are the following below.

http://opensocial-resources.googlecode.com/svn/spec/trunk/Social-API-Server.xml

http://opensocial-resources.googlecode.com/svn/spec/trunk/Social-Data.xml

http://opensocial-resources.googlecode.com/svn/spec/trunk/Core-API-Server.xml

Everyone is welcome to review and provide feedback.

Matt

[Laurent-Walter Goix]

Thank you Matt, we're indeed almost there!


i still would like to get clarifications on the App-Id reference in the GET /activitystreams path before closing 2.5.1 technically.

Besides, if i remember correctly OS 2.5.1 release is bound to an IPR update, which is still pending. Any feedback on this side as well?

thanks
walter