You cannot post messages because only members can post, and you are not currently a member.
|
 READ FIRST - Messages are now moderated for new members
|
| |
I've noticed a couple of spam messages coming to this list and I'd
like to put a stop to it early. I've turned on post moderation for
new users.
If you're posting to this group for the first time, it may take a day
or two for your first messages to appear, because a human being will
have to look at what you wrote to make sure that you're not a... more »
|
|
|
Pending OpenSocial groups structural changes
|
| |
It's been one of my goals to revisit the current OpenSocial groups structure to see if we can optimize things for the current level of traffic and support available. This post is to notify you of some changes coming soon if you visit the groups interface via the web (email posters should be unaffected):... more »
|
|
|
We need to wrap <action> tag with <actions> for action contributions declaration
|
| |
In the spec I dont see we need to wrap <action> tags with <actions> but looks like the example submitted to Shindig has this: <Param name="action-contributions"><! [CDATA[<actions> <action id="org.samplevoip.chatwithper son" dataType="opensocial.Person" label="Chat" tooltip="Chat" /> <action id="org.samplevoip.callbyperso n" dataType="opensocial.Person"... more »
|
|
|
More learnings from using EE: Can we add more precision to the model?
|
| |
OK... We've been getting our (collective) ands and feet dirty with Embedded Experiences. Most of the experience (pun intended) has been awesome. But we have run into a few challenges that I'd like to get on the table for us to discuss, and from these discussions, distill a proposal for an updated EE... more »
|
|
|
Is anybody using the REST APIs?
|
| |
With all the discussion around the REST APIs, I was asked a simple question that I could not answer: Is anyone actually using the ones that are in the spec today? I'm not aware of anyone, so I figured it would be good to put this to the community. Thanks!
|
|
|
OS 2.5 vs 3.0
|
| |
Just a quick item... I noticed that in the wiki, there is a page for v3.0 spec changes and the older page for v2.0 changes that includes a variety of items that have either been completed already or are still underway. To help keeps things organized and focused for the upcoming face to face, could we also create a page specifically focused on... more »
|
|
|
Defining an OpenSocial microdata mapping in 3.0
|
| |
I think we should look at defining a microdata mapping for OpenSocial data types. Defining an OpenSocial microdata model would allow you to tag social content within a page for Search Engine Optimization, Reporting, OpenSocial "like" buttons, etc. I also think there are use cases where you could put Gadget data / EE data... more »
|
|
|
Refactor Albums/MediaItems Service into new Files Service
|
| |
I'm still working up the documentation on this particular item, but as an evolution of the CMIS alignment work done this last year, for the 3.x timeframe, we should work to deprecate the existing Album/MediaItems APIs in favor of a new generalized File API. I will have a specific write up on this no later than midweek, but wanted to... more »
|
|
|
Drop Core Data Spec Document
|
| |
The Core Data document [[link]] is overly complicated and can easily (and more effectively) be integrated into the other documents as necessary. The document itself, as it currently stands, provides extremely little value to implementors. For the sake of simplicity, let's drop it and focus on... more »
|
|
|
Deprecate the XML Format Option
|
| |
For 2.x, we deprecated the Atom format binding, and all was Good. For 3.x, I propose that we take that further and deprecate the XML format binding and focus specifically on JSON. Individual implementations would still be free to support multiple format bindings as they see fit, but within the core protocol, data... more »
|
|
|
The Federated Social Context
|
| |
The "Federated Social Context" is an expansion on the fundamental notion of shared social contextual spaces (spaces proposal) that can span across multiple, independent OpenSocial and non-OpenSocial based systems. Here's basically how it would work. Let's assume we have three users, John, Sally and Joe. Each work for... more »
|
|
|
This group is for discussions related to the design and evolution of the OpenSocial (and gadgets) specifications.