OpenSocial API Blog

The OpenSocial Explorer: A Tool For OpenSocial Developers

2013-04-05T07:17:00.004-07:00

Today the OpenSocial Foundation released the OpenSocial Explorer, a new open source project meant to help developers learn how to build OpenSocial gadgets.

One of the biggest challenges any developer faces when trying to learn a new framework or component model is how to get started. OpenSocial has a robust and mature set of features that bring a tremendous amount of power to the developer. As every developer knows, it doesn't matter how easy a platform is to understand if you don't have something to help you get started!

The OpenSocial Explorer is meant to address this exact issue. It's goal is simple: Get you up and running in minutes.

The OpenSocial Explorer provides developers with sample gadgets demonstrating how to use various features of the OpenSocial specification. It allows developers to modify those samples and quickly re-render the application to explore how those changes effect the gadget. This not only allows you an easy way to understand all the features of OpenSocial but provides a great jumping off point for getting started with your own gadget.

The OpenSocial Explorer is a community effort and we are constantly adding new samples. We are also looking to host a version of this to further accelerate the launch time.

Within in the coming months we will try to address both of these but we need your help! We are looking for people interested in contributing to the project. We welcome all contributions so if you are interested in helping out evolve the project please contribute whatever you can! See the project page for information on how to get started. We encourage everyone to contribute back to the OpenSocial Explorer, however, we realize that may not be possible in all cases. So, if you find bugs or would like new features, please create a GitHub issue.

Check out the video below and get started today!!!!

Posted on behalf of Ryan Baxter by Mark Weitzel, President, OpenSocial Foundation

Nominations are now open for OpenSocial Community Board Members

2013-03-22T06:27:00.000-07:00

We are pleased to announce that the nominations for the Community Elected Board seat are now Open! The nomination period will run from March 22, 2013 through April 5, 2013. To nominate yourself for the board, simply email officers@opensocial.org with you name, company/project affiliation, and desire to be on the board.

Anyone OpenSocial member is able to serve on the board. The only requirement to nominate or hold the position is that you must be a member of the OpenSocial Foundation. There are no membership fees to join OpenSocial. All you need to do is fill out a simple on-line membership application.

Modern Social Application Development Demands Leaner and More Streamlined JavaScript Libraries

2013-03-06T13:10:00.000-08:00

HANNOVER, Germany – March 6, 2013 – The OpenSocial Foundation today announced here at CeBIT, the world’s leading high-tech event showcasing digital IT and telecommunications solutions, the launch of a new effort to define, design and release a next generation social application tool kit. This project will include an evolution of the OpenSocial specification and a new open source effort focused on streamlining and simplifying the approach to tightly integrated collaboration across social applications for both enterprises and consumers.

“We have seen a significant evolution in the use cases and underlying technology of social enabled applications over the past 10 years,” says Matt Tucker, chief technology officer and co-founder of Jive Software. “It is time that the standards driving the interoperability between social applications evolve along the lines of a leaner, more agile approach.”

To support the project launch, OpenSocial Foundation board members including Mark Weitzel, foundation president, will represent the foundation during the CeBIT conference in Germany as well as participate in a panel on the future of social business.

The OpenSocial Foundation was established in 2008 with the charter to provide the leading and most mature standards-based component model for SaaS-delivered social business applications. As an industry recognized standards body, the OpenSocial Foundation provides the forum for social business application companies like IBM, Jive and SugarCRM as well as industry leading consulting companies including the Dachis Group to jointly define the interoperability standards for today’s rapidly growing social applications market. "We have OpenSocial support on the SAP Jam roadmap as an integral way to integrate enterprise applications in today's social workplace," says Sameer Patel, general manager of Enterprise Social Software for SAP.

In the past five years, the foundation has led the social collaboration industry with efforts in defining groundbreaking new technology developments like the Embedded Experience and Social Feeds.

"Great adoption is driven by culture and technology. Embedding social capabilities into business process and applications drives higher engagement and adoption in any organization -- and those are the core elements of achieving strong ROI,” says Sandy Carter, vice president of Social Business Evangelism and Sales at IBM “IBM continues our leadership of OpenSocial to accelerate market value while maximizing existing IT investments"

With the launch of this new effort, the OpenSocial Foundation is setting the strategic direction for the OpenSocial community on the path of defining and implementing a new approach to the underlying components of an interconnected set of socially-aware applications.

“There is no better implementation of an open standard than through an open source project,” remarks Clint Oram, chief technology officer and co-founder of SugarCRM Inc. “By committing to both an evolution of the specification and the surrounding open source projects incorporating the latest developments in HTML5, modern browser technologies and JavaScript libraries like node.js and jQuery, the OpenSocial Foundation is responding to the demands of its community.”

To participate in the definition of the next generation of open social technology standards, please contact the foundation at president@opensocial.org.

About the OpenSocial Foundation

The OpenSocial Foundation is an industry-recognized standards body dedicated to advancing the social web through community innovation and open source. Widely supported by a majority of leading consumer and enterprise social platforms, such as IBM, Jive, and SugarCRM, the OpenSocial specification fosters the development of a growing set of socially aware off-the-shelf applications. Through open source projects such as Apache Rave and Shindig, it provides a well-defined way for 3rd-party applications to richly interact with users directly in their activity stream.

Come learn more about OpenSocial at ApacheCon US in Portland this February

2013-01-28T03:00:00.000-08:00

I'm excited to announce the OpenSocial Foundations presence at ApacheCon NA in Portland at the end of February. We have two great sessions lined up...

Make #hashtags come alive using Apache Rave and OpenSocial! ( http://na.apachecon.com/schedule/presentation/196/ ) presented on Monday, February 25th at 1:30pm by John Mertic and Mark Weitzel. We will take a deep dive into how to build integrations into Apache Rave using SugarCRM. Then, we'll see how that same integration can also be deployed on other OpenSocial containers, such as IBM Connections and Jive.
OpenSocial Embedded Experiences with ActivityStrea.ms in Apache Rave ( http://na.apachecon.com/schedule/presentation/143/ ) presented on Tuesday, February 26th at 5:00pm by Matt Franklin. This presentation will show how you can take advantage of the OpenSocial support in Rave to build a stream-based user interface that offers situational awareness via ActivityStrea.ms and in-context interaction with via Embedded Experiences.

As a foundation, we are very excited to be participating in this event, and look forward to helping more people become aware of this open standard for social business middleware.

OpenSocial at IBM Connect 2013

2013-01-21T16:49:00.000-08:00

Many app developers have taken advantage of the new support for OpenSocial 2.0 for IBM Connections to build apps for the worldwide market leading social business platform.

TemboSocial, for example, has added peer recognition to IBM Connections and integrates into the activity stream and provides OpenSocial embedded apps . ISW who has built a gamification layer for IBM Connections has also taken advantage of the OpenSocial integration points. AppFusions has also used OpenSocial to integrate Atlassian's JIRA, Confluence and Stash with IBM Connections as shown in the demo below.

And there's plenty plenty more! In fact there's over 200 partners attending the Ready for Social Business Showcase at the IBM Connect reference.

With the #IBMConnect conference just a few days away, it's likely more app developers will start taking advantage of this as well. At the conference, there will be an App Dev Throwdown where 14 companies. The winner will be featured during Wednesday morning's keynote.

The conference is also a great opportunity to get even more app developers on board. At the IBM Connect conference, app developers can take advantage of the following sessions to learn how to use OpenSocial within the enterprise. Here's a list of all the App Dev and/or OpenSocial related sessions at the conference. Make sure you add them to your calendar:

AD101: Social Applications Made Easy with the New Social Business Toolkit SDK
AD103 : Social Standards Across IBM Connections, IBM Notes, IBM iNotes and IBM Domino
AD104: IBM Connections Activity Stream Integration with OpenSocial
AD206 : IBM Lotus Domino XPages: Embrace, Extend, Integrate
AD212 : Whats New in IBM Lotus Notes Widgets and LiveText: Linking Your Data to the World!
AD405: Empower your Social Business with SAP Processes in the Activity Stream
AD407: Qualifying Round for App Dev Throwdown I
AD408: Qualifying Round for App Dev Throwdown II
BP209 : In The Land of Social Apps, the API is King
CUST108: How 3M Integrated SAP into the Activity Stream Using OpenSocial
ID101 : What's New in IBM iNotes 9.0 Social Edition
INV110: App Dev Strategy: Coding Social Business Applications
INV211 : The New Social Business Paradigm with OpenSocial
INV213: The Roadmap for Enterprise Social: From Social Email to Universal Activity Streams
JMP102 : Extending Your App Arsenal With OpenSocial
JMP202: Extending IBM Connection to Build an Exceptional Social Learning Platform
SHOW301: Becoming a Connections Developer: Lessons from the Field

Follow along @IBMConnect.

As you can see, with IBM's backing of OpenSocial 2.0, OpenSocial continues to take over the enterprise!

Posted on behalf of Luis Benitez

OpenSocial Foundation Events for Q1 2013

2013-01-07T13:51:00.000-08:00

Happy New Year everyone! We hope 2013 will be as promising and rewarding of a year as it's shaping up for OpenSocial. We are excited to announce us being a part of several events this quarter...

IBM Connect

Once again there will be lots of OpenSocial going on at IBM Connect, going on in Orlando from January 27th thru the 31st. In the exhibits area stop by the IBM Signature Solutions Area to see how OpenSocial is being leveraged to extend the reach and integration of Social Capabilities to third-party applications. You'll learn more about OpenSocial and other standards are driving innovation for integration across business applications.

There also are a number of OpenSocial related sessions, namely...

INV211 : The New Social Business Paradigm with OpenSocial
AD103 : Social Standards Across IBM Connections, IBM Notes, IBM iNotes and IBM Domino
AD206 : IBM Lotus Domino XPages: Embrace, Extend, Integrate
AD212 : Whats New in IBM Lotus Notes Widgets and LiveText: Linking Your Data to the World!
ID101 : What's New in IBM iNotes 9.0 Social Edition
BP209 : In The Land of Social Apps, the API is King
JMP102 : Extending Your App Arsenal With OpenSocial

ApacheCon NA

We will also be a part of ApacheCon North America 2013, going in Portland, OR from February 24th thru the 28th. The official conference, trainings, and expo of The Apache Software Foundation (ASF), ApacheCon draws Open Source users, developers, gurus, students, novices, community managers, and enthusiasts to address today’s issues, opportunities, and solutions focusing on the ASF’s nearly 150 projects and initiatives. With both Shindig and Rave as official Apache projects, we will be bring the OpenSocial message through two sessions...

Make #hashtags come alive using Apache Rave and OpenSocial! - http://na.apachecon.com/schedule/presentation/196/
OpenSocial Embedded Experiences with ActivityStrea.ms in Apache Rave - http://na.apachecon.com/schedule/presentation/143/

CeBIT 2013 - Hannover, Germany

We will also be at CeBIT in Hannover, Germany, which is the world's largest and most international computer expo. Held each year on the Hanover fairground, it is considered a barometer of the state of the art in information technology. We are excited to have a panel discussion with several OpenSocial Foundation board members, along with foundation president Mark Weitzel, on one of the stages. In addition, look for OpenSocial foundation members SugarCRM and IBM exhibiting, and come visit the OW2 village.

We look forward to having more events in 2013 to bring the OpenSocial message to the social business community.

OpenSocial Foundation becomes OW2 Consortium Associate Member, announces availability of OpenSocial 2.5 specification

2012-11-30T12:28:00.001-08:00

Paris, France – November 30, 2012 – OpenSocial Foundation announced today on becoming an OW2 associate member. This formal relationship brings two market-leading open foundations together, bringing the message of social cloud middleware to a larger worldwide market. OpenSocial Foundation is a Platinum sponsor and exhibitor at this year’s OW2Con, with foundation president Mark Weitzel keynoting today on how open standards and open source are driving social business.

“The OpenSocial Foundation continues its commitment to reaching out across the industry to build a robust social business ecosystem. We are excited to work closer with OW2 and it’s consortium members to further advance standard based social middleware.” said Mark Weitzel, President of the OpenSocial Foundation

"We were excited to have OpenSocial as a Platinum sponsor of OW2 Con this year." said Cedric Thomas, CEO of the OW2 Consortum. "With the growth of cloud computing and SaaS delivered social business applications there is a great deal of synergy between OpenSocial and OW2. It only seemed natural to find ways to align our efforts more closely together. We look to move away from legacy portal systems and towards social systems of engagement, we look forward to working with the OpenSocial and Apache Rave communities to define and build the next generation open, standards based, social platform."

Announcement of OpenSocial 2.5 specification.

In addition, the OpenSocial Foundation also announces today the general availability of version 2.5 of the OpenSocial specification. This release adds in new features that were previously in incubation, such as the Common Container, which formalizes the APIs for application lifecycle and management, as well as adds new capabilities such as the ability to introspect the services with an OpenSocial platform through a metadata API.

“OpenSocial provides the leading and most mature standards based component model for SaaS delivered social business applications.”, said Mark Weitzel, President of the OpenSocial Foundation.
“Version 2.5 continues to set the benchmark for community driven innovation and fosters interoperability, choice, consistency, innovation, and quality between social platforms and 3rd party applications.”

For a more complete list of the changes, see the full release notes at http://bit.ly/os25publishedspecissues, and you can download the full specification at http://docs.opensocial.org/display/OSD/Specs.

About OW2
Founded in January 2007, OW2 is an independent industry community dedicated to developing open source code infrastructure and to fostering a vibrant community and business ecosystem. The OW2 Consortium hosts some one hundred technology Projects, including ASM,Bonita, eXo Platorm, Funambol, JOnAS, Joram, Orbeon Forms, PEtALS, SpagoBI and XWiki. More information at: www.ow2.org.

About OpenSocial
The OpenSocial Foundation, an industry recognized standards body, dedicated to advancing the social web through community innovation and open source. Established in 2008, the Foundation provides the leading and most mature standards based component model for SaaS delivered social business applications. Widely supported by a majority of leading consumer and enterprise social platforms, such as IBM, Jive, and SugarCRM, the OpenSocial specification fosters the development of a growing set of socially-aware off-the-shelf applications. Through open source projects such as Apache Rave and Shindig, it provides a well-defined way for 3rd party applications to richly interact with users directly in their activity stream. For more information, visit www.opensocial.org.

Come see us at OW2Con and be a part of the OpenSocial EU Workshop!

2012-11-20T07:14:00.004-08:00

We are excited to announce we will be in Paris from November 27-29, 2012 to be a part of OW2Con. OW2Con is the annual conference for the OW2 consortium, which is an open source foundation focusing on open source middleware components. OpenSocial aligns nicely with that, and as such we are excited to be one of the Platinum sponsors for the event. Mark Weitzel, president of the OpenSocial foundation, will be keynoting at the conference on the changing landscape of social business and how open source is a part of it.

In addition, we will be holding a one-day workshop on November 27th, highlighting the shift to Social Middleware components in the industry today. We'll showcase how various companies are adopting this today and how they are doing it, and will provide the opportunity for hands-on demos of the technology and learning how to begin building OpenSocial container objects and leveraging embedded experiences. Learn more about the day's schedule at http://www.ow2.org/view/OW2Con-2012/OpenSocial_Workshop.

Both events are free to be a part of, but advanced registration is requested. You can register for the events at http://www.ow2.org/view/OW2Con-2012/OpenSocial_Workshop_Register . We look forward to seeing everyone there!

Taapi Plans to Enable OpenSocial Gadgets in Energy Game!

2012-10-03T06:23:00.002-07:00

A team of mobile and gaming industry experts have collaborated to create and launch Taapi, an entirely new type of social game that uses the power of gamers around the globe to save energy.

The game is the first global, mobile gaming platform that will have a significant impact on the real-world. Available via iOS for iPhones, iPods and iPads, Android, and the web, Tappi awards players points for being the first to shut off unused lights.

So, how does it work?

People tap in to Taapi to provide blocks of time where their homes (and lights) are available to the game for shut off. When a home is tapped in, it’s lights are anonymously added to a ‘pool’ of other lights that are waiting to be turned off.

Meanwhile, gamers race to be the fastest to turn off lights from that pool as soon they become available.
Gamers get the satisfaction of knowing that they are turning off lights all over the world that are not being used. All with just a tap.

Gamers will have the ability to choose challenge games, geographies, light types, or random selections while playing to get to turn lights off from the pool of waiting lights. Every light and location is completely secure. Lights in the pool waiting for turn off are anonymous and not individually identifiable in any way.

Taapi leverages crowdsourced players to act on unused lights that are available in the pool for shut-off and rewards both players and the households that use Taapi. By being on Taapi, homes will benefit from saving money on their energy bills and also get points for every minute their lights are available to the game.

If some players want to keep their home’s lights all to themselves-that works too. Households can use Taapi to control only their own lights and create a local Taapi group of players within their WiFi network. They still get points for using Taapi and a nifty home control panel in the app.

The Taapi team has brought some powerful partners into the energy-gaming spotlight with them. Amazon is slated to fulfill orders for the Taapi in-home products and smart-chip giant NXP will be providing chipsets.

Taapi is appealing to a range of developers by providing a full API to provide hooks that can programmatically act on Taapi's services.

The Taapi API will provide access to features such as:

Adding new players
Authenticating players
Calling player stats
Calling general country, energy, and date stats
Initiating a race session
Obtaining the stats for a unique race session
Polling for available races

Taapi has selected Atlassian (http://atlassian.com) products for community support, Mashery (http://mashery.com) for API hosting and they have a built-in an OpenSocial container for developers to write gadgets for Taapi using the OpenSocial (http://opensocial.org) standard.

Taapi & OpenSocial

Taapi's OpenSocial container support will allow developers to quickly and easily write OpenSocial compliant gadgets that can call and serve a number of Taapi features like public Taapi use statistics, aggregated stats, individual users stats and game session availability.

The Taapi OpenSocial container will support gadget authentication via OAuth to enable personalized, contextual player information and interaction as well. Players will be able to add approved gadgets to their instances of the Taapi game and extend Taapi's functionality.

For example, a developer could write a 'My Country' Taapi gadget to alert a player when a session in a specific country is available, authenticate them, opt them into the game session and tweet about their participation, all in that country's native language(s).

Taapi founder Carol Glennon states, "Support for an accelerated development process was one of our top goals for the Taapi platform. Enabling gadgets through our OpenSocial container makes it easy for developers to gain fast access to our API while writing cool gadgets that users can use in Taapi right away."

Taapi has already distributed in-home prototypes to create a seed pool of lights that can be acted upon by players and is expected to launch their mobile suite over the next few months.

Learn More!

Watch the Taapi movie
Visit Taapi for the latest news and updates
Get more information about Apache Rave and OpenSocial

Posted on behalf of Don Martelli, Chief Marketing Officer, Taapi, by Mark Weitzel, President, OpenSocial Foundation

About Taapi

The Taapi core executive team have been working on projects together for the last four years and have experienced amazing success in that time. Together, they have a fantastic history of ability with the proven results to deliver this project in a timely manner. Examples of previous work includes delivering mobile apps, games as well as cutting edge and complex 3D animations and solutions for Fortune 500 companies including Time Warner, Intel, CBS, California Tourism, Delta Airlines and National Geographic. We have been recognized and received over a dozen National and International awards for our work and have been at the cutting edge of technology for a combined four decades.

OpenSocial Powers Scientific Research Communities

2012-08-20T05:07:00.000-07:00

Palo Alto, CA -- The OpenSocial Foundation today announced that the biomedical research networking community (think "distributed LinkedIn for cancer researchers") with the help of the OpenSocial Research Networking Gadgets (ORNG) initiative, and two major open source research networking platforms are adopting OpenSocial.

“The vision of making our research networking systems OpenSocial platforms so that independent applications can be built and shared amongst institutions is now coming to fruition at the required scale,” said EricMeeks, a founder of ORNG and lead technical architect for the Clinical and Translational Science Institute (CTSI) at the University of California, San Francisco (UCSF). “This will allow us to expand our research systems from researcher discovery to researcher collaboration, and perhaps most importantly cross-institutional research collaboration, without forcing us to rebuild the online collaboration tools that are currently found in commercial networking systems.”

Earlier in July, the VIVOplatform for scientific collaboration and discovery, formally announced support for OpenSocial in version 1.5. VIVO has a number of major partner institutions, including the University of Florida, Cornell University, the University of Indiana, and Scripps, among many others.

"The VIVO team is working to encourage independent development on the VIVO platform, and support for the ORNG initiative is a significant step in that direction. We are eager to see how the research networking community responds to this initiative, which joins the flexibility of the OpenSocial standard with the expressive power of semantic data,” said Jim Blake, VIVO technology lead at Cornell. “The upcoming VIVO Conference will provide a focus for discussion and exchange of ideas, with both a workshop and a panel discussion dedicated to OpenSocial and ORNG."

After several years of support as an unofficial add-on, the Profiles Research Networking Software platform will be bundling OpenSocial into the core product. Profiles was developed for Harvard Catalyst: The Harvard Clinical and Translational Science Center under the supervision of Griffin M. Weber, MD, PhD, chief technology officer at Harvard Medical School.

“By enabling different research networking platforms to share a common approach to implementing front-end tools, OpenSocial has benefits for multiple stakeholders,” Weber said. “Software developers can use the same code to add new functionality to multiple products; institutions can more easily make decisions about which platform to adopt; and researchers who are part of cross-institutional teams will have a similar user experience when collaborating online.”

UCSF’s Meeks pioneered the integration of OpenSocial and Apache Shindig into these platforms. He's now working to develop an app directory (as with Apache Rave), and is working with the OpenSocial Foundation to engage a community of developers. OpenSocial app development in research networking will be a major topic covered at the annual VIVO conference in August.

“This is an excellent example of how an open, community driven specification enables a broad and vibrant ecosystem. It’s exciting to see how and entire industry segment is working together to move the social Web forward,” Meeks said.

To learn more about OpenSocial, visit www.OpenSocial.org.

Information about VIVO is available at http://vivoweb.org/

The VIVO conference Web site is http://vivoweb.org/conference

Information about Harvard Profiles is available at http://profiles.catalyst.harvard.edu/.

Posted by Mark Weitzel, President, OpenSocial Foundation

Apache Rave & Apache Shindig "Beer Forge" at OSCON 2012!!

2012-07-11T09:27:00.001-07:00

It's a party!!

To help kick off OSCON, the OpenSocial community is excited to host the first Apache Shindig / Apache Rave "beer forge"! We've got space at The Spirit of 77 sports bar just a few blocks away from the OCC on Tuesday, July 17th for a chance for us to get together and have a few pints on OpenSocial!

You'll have a chance to meet the leaders of our open source community that are working to move the social web forward through the Apache Shindig and Apache Rave projects. There will be plenty of opportunity to learn first hand how some of the industry's leading social platforms from IBM, Jive, Mitre and others are leveraging open source technologies in their products.

Plan to start off OSCON with the OpenSocial community and enjoy some good food & great beer as we celebrate another year of advancing the social web through open source!

Online Ticketing for Apache Shindig / Rave Meetup powered by Eventbrite

Note: Make sure to RSVP so we can check you in at the event and have an accurate count of who's coming. Thanks!!

OpenSocial State of the Union, 2012

2012-07-11T08:43:00.001-07:00

I'm excited to announce that this year's "State of the Union" event will be held on Tuesday, July 17, 2012 at the Jive's offices in Portand Oregon. It lines up with OSCON, the premier conference for open source technologies. We'll have discounted passes for the conference, so be sure to check out the OSCON site for all the detailed information about that event. If you just want to grab some swag, we'll also have "Expo Only" tickets as well.

While past State of the Union events have been structured as a "mini conference", this year we've decided to take a different tact. The Foundation's primary goals are to enable our community in developing open standards and technology that advance the social Web and foster a vibrant, open ecosystem of social platforms and applications. This year's event will be a series of working sessions where we will focus on specific topics that, as a community, we need to address in the upcoming year. Each session will be moderated to keep us on track. The moderator will produce an "action plan" that we'll use to track our progress and measure our results.

Space is very limited, so please be courteous to your fellow "OpenSocialites" RSVP if you plan to attend in person and are ready to roll your sleeves up and pitch in.

For additional information visit the event page on the OpenSocial wiki or the eventbrite link below.

Online Ticketing for OpenSocial State of The Union - 2012 powered by Eventbrite

Happy Coding!

Mark Weitzel, President, OpenSocial Foundation

Announcing Apache Rave: A new web and social mashup engine!

2012-03-27T19:32:00.000-07:00

Today the Apache Software Foundation announces the Apache Rave project as new Top-Level Project.

Apache Rave is a new Open Source software mashup platform that allows developers to build and engage with an array of social network technologies such as OpenSocial, W3C Widgets, and Activity Streams.

The project started only a year ago, March 1 2011, when entering the Apache Incubator as a collaborative effort by individuals from a wide range of corporations, non-commercial organizations, and institutes from around the world and was seeded by code donations from The MITRE Corporation, Indiana University Pervasive Technology Institute, SURFnet, OSS Watch, Hippo, and numerous individual developers.

Rave builds on open standards and leverages and aligns with other open source projects like Apache Shindig and Apache Wookie to deliver a lightweight, flexible, widget-based platform that easily scales across federated application integrations, social intranets, and multi-channel social communities with enhanced personalization and customized content delivery.

Besides supporting the OpenSocial standard, Apache Rave generalized the concept of widgets to also, and transparently, support W3C Widgets. And through its open and pluggable API adding support for other widget containers and renderes can easily be added.

Members of the Apache Rave project are also active participants and contributors of the OpenSocial Foundation and the W3C organization, and directly involved in Apache Shindig, Wookie and many other related open source projects. Apache Rave is truly a community driven open source project and already is building up a lot of interest from commercial, non-commercial, governmental and individual developers across the globe. The ASF announcement references several high profile organizations using and contributing to Rave today, and of course the project is looking for more!

Please meet and join us at http://rave.apache.org

Posted on behalf of Ate Douma & the Apache Rave Team by Mark Weitzel, President, OpenSocial Foundation

Here we go! Next rev of the specs are officially under development!

2012-03-02T21:12:00.001-08:00

On Tuesday, February 28, the OpenSocial community came together to officially kick off the next round of development on the specification. It was a long, but very productive day. You can read the minutes of the meeting on the wiki.

I would like to thank all of those who travelled in from out of town to attend the meeting in person, as well as those that joined via video conference. Especially the folks from Europe that stayed late into their evening. I would be remiss if I also did not thank Rajat Paharia from Bunchball for giving a great talk about gamification and how an open, community driven standard could be used as an accelerator for the adoption of game mechanics in enterprise.

There are three other individuals that deserve a big round of "Thanks". James Snell (IBM) and Matt Franklin (Mitre) graciously volunteered their time and stepped up to the plate as spec editors. I will tell you from past experience this is no easy task. There are a tremendous number of areas in the spec that need to be cleaned up, where proper diction and examples will be paramount to ensuring clarity and consumeability. This is on top of the hundreds of other little details that will come up requiring their attention and consuming their time. And finally, Matt "the Hun" Marum (IBM) has agreed to continue his work as Release Manager. We affectionately gave him this nickname because he's the guy who will kick us into shape and make sure we make our dates.

There's a lot to do between now and May, and that's just for 2.5! We'll be starting the 3.0 work right after that. Given the creativity, passion, and dedication that I saw over the last few weeks that culminated in the kickoff, I've got no doubt we are in for another fantastic release of the spec.

--Mark Weitzel

President, OpenSocial Foundation

OpenSocial Version 2.0.1 Final open for voting

2011-11-16T11:26:00.001-08:00

Version 2.0.1 of the OpenSocial specification has been released for voting. One of the major updates to the specification is finalized support for the OAuth 2.0 specification.

For more information on the changes to the specification and related components, please see the voting thread and file diffs here.

Jonathan LeBlanc (@jcleblanc)
Jonathan LeBlanc is a principal developer evangelist with X.commerce. Jonathan has been a member of the OpenSocial community for over three years and is the author of O'Reilly's "Programming Social Applications".

Join The W3C Social Business Jam

2011-10-19T08:46:00.000-07:00

OpenSocial made significant strides over the past year with the introduction of new capabilities, and broadening its support and alignment with other standards like Activity Streams (http://activitystrea.ms/) and OAuth 2.0 (http://tools.ietf.org/html/draft-ietf-oauth-v2-22). One of the fundamental tenants of the community is to engage across the standards ecosystem to leverage adjacent standards and technologies when and where possible.

One way to continue the momentum of OpenSocial is to make a clear connection between the specification, the standards it includes and the needs of businesses. Social technologies are changing the businesses that have embraced and applied them but not not only for media. Businesses are using social technologies to better connect with partners, suppliers and employees -- as well as with customers.

But how are the ideas, technologies and standards in the social space holding up as business-use cases are applied ?

The W3C Social Business Jam is a global, online conversation with business leaders, subject matter experts and like-minded individuals about the current state of social business, the future role that social technologies can play in improving the bottom line, and how social technology should evolve in order to support business objectives. A primary objective of the Jam is to cooperatively explore key trends and concepts in social business with an eye towards how social standards can facilitate business goals. The Jam should produce a better understanding for participants of how businesses are using social technologies and the challenges they face integrating the technologies into their existing environments.

Mark Weitzel, president of the OpenSocial Foundation, is one of the noted hosts for the Jam. While Mark will be an active participant throughout the Jam, he is hosting a conversation on the Seamless Integration Of Social from 12 pm to 4 pm US eastern time on November 8.

Come share your insights and opinions. Registration is open and free, and takes just a few moments of your time. For more information, go to : http://www.w3.org/2011/socialbusiness-jam/

David Robinson

Bring OpenSocial gadgets to Moodle

2011-10-17T15:14:00.000-07:00

We present here a plugin that allows to bring OpenSocial gadgets into Moodle. OpenSocial gadgets are rendered via Apache Shindig (extension of version 2.0 that supports Spaces).

Moodle is a Learning Management System used in many Educational Institutions (Universities) to manage courses. It is a plugin based PHP application that can be extended by installing additional modules. These modules have to be installed on a Moodle server by a system administrator. The Moodle view usually consists of a main center area and a rather narrow right column with blocks. The center area normally contains main resources, such as, wiki, forum, lesson, quiz, etc. The right block contains some helper plugins, such as, calendar, upcoming events, latest news, recent activity, etc. These are to extend the functionality of the main page.

There are two different OpenSocial plugins for moodle. The first one adds a new module to Moodle. It is very similar to pages in moodle, however in addition, OpenSocial gadgets can be specified. Once it is installed, a teacher can choose a "Widget space" to be added to the course and specify OpenSocial gadgets for it. The teacher can choose whether 1,2,3 column view should be used for gadgets.

The resulting outcome is the iGoogle similar view where students can work with gadgets.

The second plugin adds a new block to Moodle. Teacher can add OpenSocial gadgets to the right
column for already existing in Moodle wiki pages, lessons, forums, etc.

One of the main benefits is that the big pool of OpenSocial gadgets can be used by teachers. Thus, once the OpenSocial plugins are installed in Moodle, a teacher can extend the functionality of Moodle without bothering system administrators with plugins installation. The teacher can add and remove gadgets easily and even can write her own ones. The plugins greatly improve the flexibility in choosing the resources and applications for the course specifics. OpenSocial gadgets can be found in the open widget repositories, such as, Role Widget Store, iGoogle Directory, etc.

In addition to reuse of applications existing in the Cloud and flexibility in choosing applications for the course, contextual gadgets and OpenSocial API are the other additional benefits.

Space extension allows gadgets to adapt to a specific context. For example, wiki gadget saves data for a course and manages access to itself only by people engaged in this course. The same wiki gadget will behave differently being added to another course (different wiki history and different people to access it). Such space extension is already used in production in Graaasp and planned in Apache RAVE project.

OpenSocial API brings the standard way to retrieve and exchange social information between different Moodle installations and other social networks, that improves data portability and interoperability.

Plugins work for new version of Moodle 2.1. It should work for Moodle 2.0, though it was not tested. The installation instructions and source code can be found at github:
OpenSocial Moodle module
OpenSocial Moodle block

This plugin was developed within the ROLE Integrated Project and is already used in 5 courses at Shanghai Jiao Tong University.

Evgeny Bogdanov

OpenSocial 2.0 Brings Us Closer to the Socialized Enterprise

2011-09-20T14:36:00.000-07:00

Now that the final version of the OpenSocial 2.0 spec has been announced, we at Wrike, as one of the companies leading the charge on social collaboration, are excited about seeing more enterprises lean into this type of integration. In fact, we’ve just developed our own OS 2.0 widget, which will help transform email functionality within Wrike’s collaboration tools. But before we tell you more about that, here’s why OpenSocial has our collaborative juices flowing.

Open season for innovation

It’s a safe bet that the typical iPhone user is used to working with direct access to multiple apps that can help him work and play more effectively. iPhone Marketplace was a bigger source of innovation for users than the phone hardware itself. Many enterprise solutions miss that open ecosystem opportunity today. For example, Outlook has millions of users spending their whole working days in front of it, who would love the same type of easy access to useful apps that would enhance their workflow. Yet, how many of those users installed Outlook plug-ins? OpenSocial 2.0 has the potential to open up innovation for enterprise software, bringing the right apps with the right integrations in a safe package, directly in front of users who want to benefit from them.

Bridging gaps between the apps

The improved safety, compatibility and connectivity that the OpenSocial standard offers, makes it a lot easier to build bridges between useful enterprise apps. Bridges that go beyond simple data integrations into the land of fully integrated user experiences. Taking my own company, Wrike, as just one example, we’re based on the belief that project management tools should be inherently social, and this is a fundamental part of our value proposition to companies around the world. So, it’s easy to see why OpenSocial has us excited about ways we can keep improving our users’ experience and their productivity, by plugging into the networks and tools they are already comfortable using.

Potential to turn email into a structured, real-time platform

A couple of days ago, Wrike’s widget appeared in the OpenSocial 2.0 sandbox with examples of embedded experiences in the activity stream, emailbox and a compact dashboard. I’d like to focus a bit more on the email component of the widget and share why we see great potential in it.

Email software has effectively been on “lock-down” since its inception. When you receive dozens of emails on a daily basis, it gets really challenging to turn that type of inbox chaos into the cohesive big picture of your projects and goals. From the start, a key pillar of Wrike’s product vision has always been to open up that software and bring emails into a centralized system, turning long email discussion threads into neat plans. This is why Wrike created its email integration, which allows users to create, assign, schedule and discuss tasks right from their inboxes.

Today, people use email even more than when Wrike was conceived. So, instead of try to push email out of the office toolkit “nest” (which seems like a hard and unproductive thing to do), we wanted to leverage the good things about it. OpenSocial 2.0 gives us new opportunities to implement our exciting idea – to turn 40-year email functionality into a structured, well-organized, real-time platform that supports sharing, discussions and other actions you need for collaboration. Wrike’s widget brings emails to life and integrates them fully into the project management process. Users don’t even need to change anything in their working habits.

In parallel with developing our widget for OpenSocial 2.0, we’ve been working on Wrike’s new add-on for Outlook. For the end user, the experience will be very similar to what they get with our OS widget. However, if we look at it from the development side of things, building this add-on atop Outlook is a more laborious and complicated process, a whole other world. That’s where we see the big difference between open platforms and closed systems – in how easily can you plug into them.

With the potential that OpenSocial 2.0 offers and the ease that you can build widgets on top of it, I believe that the world will quickly become attuned to getting this kind of experience for many more email clients. People still strongly rely on email in their work and they just need a way to naturally bring those messages into their collaboration process. So, it turns out that email isn’t dead as some claim, it just needed a rebirth, And OpenSocial 2.0 is an essential part of that evolution.

What’s next?

The new generation of apps, built on the open platform, will bring a new wave of innovation and productivity. OpenSocial has already gained support from many players in the enterprise software market. I’m sure we can expect new marketplaces and ecosystems, and faster innovation as others follow suit.

Users will of course be the ones to benefit, but it’s a win-win for everyone, as we continually find new ways to improve the way that we work. Your company’s mission should they choose to accept it? To socialize the enterprise.

Andrew Filev (@andrewsthoughts)
Andrew Filev is a software entrepreneur with more than 10 years of experience in project and product management. He is the founder and CEO of Wrike, a Silicon Valley-based provider of project management and collaboration software. To learn more about Andrew and his views, you can subscribe to his Project Management 2.0 blog or follow him on Twitter (@andrewsthoughts).

Announcing a New OpenSocial and Emerging Social Technology Book

2011-09-08T16:18:00.000-07:00

I'm happy to announce that, as of yesterday, Programming Social Applications is officially out in print. I normally wouldn't post on the OpenSocial blog about my own book but the content is specifically designed for this community, so it's a good fit. Within the book I cover topics on:

Building social applications and containers using Shindig and OpenSocial.
The vast array of features and functionality within the OpenSocial specification.
Front-end code security tools like Caja and ADsafe.
Authentication systems with OpenID
Authorization systems with OAuth 1.0a and 2.0
Emerging social technologies like Activity Streams, Open Graph Protocol, PubSubHubbub, Salmon and others.

I will be conducting a webcast through O'Reilly on October 4th, 2011 at 1pm PDT to talk with everyone about the technology within the book and explore some of the interesting emerging technologies that are upcoming. More details to come shortly.

You can purchase the book here or get a free sample here. For those of you that pick up the book, remember that Chapter 12 (OpenID / OAuth hybrid extension), Appendix I (Environment Setup) and Appendix II (Terms) are offered as an online only download from O'Reilly since the book was getting a little large and we didn't want to simply delete content.

Please send feedback and tell me what you think - I'd love to hear from the community!

List of OpenSocial Containers

2011-08-25T13:45:00.001-07:00

Recently there was a thread going around the OpenSocial and Gadgets Specification discussion board about providing an updated list of OpenSocial containers, both at the open and enterprise levels.

From this discussion, we have put together a living document to provide a list of those OpenSocial containers and implementers that we are aware of, including links to their associated information pages or developer networks. You can view the list here.

We Need Your Help

Since this is a living document, the content will always be changing as new containers surface or if we have left something off of the list. For everyone working with different container implementations, we ask that you review the list and help update the content if something is incorrect or missing. We really need the help from container implementers, users and those of you with an extensive OpenSocial container knowledge base to help out.

Thank you everyone.

Announcing the Release of the OpenSocial 2.0 Specification

2011-08-18T16:28:00.000-07:00

Following the 11:59 PDT voting cutoff last night, version 2.0 of the OpenSocial specification has officially passed with 22 positive and 0 negative votes.

Version 2 of the OpenSocial specification opens up integration with other well known open source social specifications, ties in both a simplified gadget format as well as new powerful tools, plus announces some deprecated features.

Some of the major revisions to the specification include:

Activity Streams support: Activity Stream provides a mechanism for defining rich and detailed social activities, defined in a simple actor / object / target format. The adoption of this open specification allows OpenSocial to not only provide richer data sources but also to be interoperable with more open streams.

Deprecated support for ATOM: It was determined that the ATOM serialization format for OpenSocial information was not being utilized in practice. Since there were a number of adjacent specification utilizing JSON for the preferred data format, the community has decided to deprecate support for ATOM.

Simplified gadget format: Providing a mechanism for embedding template libraries into a gadget specification file, the ability to integrate data pipelining and templating features within a gadget has been greatly simplified.

Embedded Experiences: The community saw a need to provide a mechanism for providing embedded experiences directly within the gadget. By integrating these features, the content host is able to tell a service how to render its content instead of having the service figure it out themselves. This will provide a higher degree of control over data in a gadget.

New Incubating API
- OAuth 2 support: The OpenSocial 2.0 specification now includes support for OAuth 2. Since the OAuth 2.0 specification has not been finalized by the time of this release, OAuth 2 support is currently in an incubating mode. Currently revision 20 of the OAuth 2 specification is being integrated. Support for OAuth 1.0a is still included in the OpenSocial 2.0 specification and has not been deprecated.
- Common Container: In OpenSocial 2.0, a new optional specification has been added for a common container API. The goal is to simplify the container and gadget integration model. It provides a set of common services that Container developers can leverage for features like in-browser Gadget lifecycle event callbacks, embedded experiences, and selection and action handlers.

Here are a few links that will help you get up to speed on the recent changes and additions:

In addition to this announcement, Andrew Davis has another piece of great news on the Shindig side:

Along with releasing the OpenSocial 2.0 spec today, the OpenSocial Foundation is working together with our members companies, and implementor friends at Shindig are proud to announce the availability of the first OpenSocial 2.0 Container, running the latest Shindig 3.0 build, the Open Social Sandbox, at http://sandbox.opensocial2.org:8080/. The site is a live demo of the latest features of the OpenSocial 2.0 spec including Embedded Experiences, Declarative Actions, OpenSearch and powerful new open gadgets APIs to enable gadgets to jump out of the box. The site provides tutorials, demo videos and is geared towards enabling gadget developers immediately to build new gadgets, and test them out on the site through the "Customize" button.

Lastly, I wanted to say thank you to the entire community and dedicated participants who have made this major release possible.

Vote Now! OpenSocial and Open Source Presentations at SXSW

2011-08-17T18:12:00.000-07:00

As a followup to our OpenSocial and SXSW Interactive 2012 post last month, we wanted to make available the links to the OpenSocial and associated technology proposals that have been submitted to the conference.

We would all greatly appreciate it if you could vote up these proposals to ensure that we have a technology presence at the conference next year, presenting the extensive new technology stack that is inherent within OpenSocial 2.0. There are a total of 3178 proposals in for this year and 30% of the decision-making process is up to community votes, so the more votes and comments we can get the better.

The proposals that we have available are:

Distributed Web Frameworks: The Future of Social
Link: http://panelpicker.sxsw.com/ideas/view/10692

Revolution! Open Apps Will Change the Enterprise
Link: http://panelpicker.sxsw.com/ideas/view/12817

Building Social Apps for Business Using Opensocial
Link: http://panelpicker.sxsw.com/ideas/view/12187

If you have a proposal on the technology or features behind OpenSocial I'd be glad to add it into this blog post - please comment on this post with the details.

Thanks everyone.

Building Dynamic Applications with Data Pipelining, Templating and YQL

2011-08-10T16:12:00.000-07:00

Hello again everyone,

Today I wanted to go over one of the interesting things that you can do with OpenSocial using templating and data pipelining. Since these were introduced in version 0.9 of the specification, this functionality will not be available if:

The container that you are using does not support OpenSocial version 0.9 or later.
The container that you are using does not support data pipelining or templating.

With that said, let's get right down to an example. For this example, we're going to go through a few steps in order to scrape and display the recent headlines from Reddit:

We will use data pipelining to load in the headlines from Reddit.
The URL of the data pipe will be a dynamic call to the Yahoo! Query Language (YQL). YQL will be used to scrape the HTML from the page, then use an xpath to drill down to the repeating anchor tags that denote the headlines.
Lastly, from the JSON data that is returned back from YQL into the data pipe, we're going to use OpenSocial templating to display out the headline results.

Let's take a look at the gadget code behind this:

<?xml version="1.0" encoding="utf-8"?>

<Module>

   <ModulePrefs title="Reddit Headline Fetch"

      title_url="http://www.jcleblanc.com"

      description="Obtains reddit.com headlines via YQL"

      author="Jonathan LeBlanc">

      <Require feature="opensocial-0.9"/>

      <Require feature="opensocial-data" />

      <Require feature="opensocial-templates" />

   </ModulePrefs>

   <Content type="html">

   <![CDATA[

   <script type="text/os-data" xmlns:os="http://ns.opensocial.org/2008/markup">

      <os:HttpRequest key="reddit" href="http://query.yahooapis.com/v1/public/yql?

      q=select%20*%20from%20html%20where%20url%3D%22http%3A%2F%2Fwww.reddit.com

      %22%20and%0A%20%20%20%20%20%20xpath%3D'%2F%2Fa%5B%40class%3D%22title%22%5D'

      &format=json"/>

   </script>

   <script type="text/os-template" require="reddit">

      <ul>

         <li repeat="${reddit.content.query.results.a}">

            <a href="${Cur.href}">${Cur.content}</a>

         </li>

      </ul>

   </script>

   ]]>

   </Content>

</Module>

Let's break down the components of this gadget. First let's start with the meta data within the <ModulePrefs> node. There are three features that we will need to require:

   <Require feature="opensocial-0.9"/>

   <Require feature="opensocial-data" />

   <Require feature="opensocial-templates" />

First we have the OpenSocial version that we want to include. For our needs we can include version 0.9 of the specification since that will allow us to include the other features we need, namely our second and third Require statements for opensocial-data (Data Pipelining) and opensocial-templates (Templating). These three will give us the features that we need for the example.

Next we have the innards of the <Content> node. Let's explore the first <script> block:

   <script type="text/os-data" xmlns:os="http://ns.opensocial.org/2008/markup">

   <os:HttpRequest key="reddit" href="http://query.yahooapis.com/v1/public/yql?

   q=select%20*%20from%20html%20where%20url%3D%22http%3A%2F%2Fwww.reddit.com

   %22%20and%0A%20%20%20%20%20%20xpath%3D'%2F%2Fa%5B%40class%3D%22title%22%5D'

   &format=json"/>

   </script>

This is our data pipelining section. When the gadget loads in the container that we are running it in, this section will issue an HTTP request to populate an object with the return value of the request. In our case this will be a GET request to the YQL service.

To define a data pipe, we set the type of the script block to text/os-data and then define the os XML namespace. Within the script block, we set the object that we want the data returned to to be "reddit". We then issue a data pipelining HTTP GET request to the YQL service, using the href attribute. This URL used includes the following components:

The public YQL URL: http://query.yahooapis.com/v1/public/yql
q: The YQL query to run, placed as a query string parameter.
format: The format to return our data in, in our case JSON. This is also placed as a query string parameter.

If we look at the query that we are using, we can see what the components of the request are:

  SELECT * FROM html WHERE url="http://www.reddit.com"

  AND xpath='//a[@class="title"]'

YQL uses a query syntax much akin to SQL. In our request we are using the html table, which defines request functionality to allow us to scrape data from an HTML page and then apply an xpath to drill down to the nodes on the page that we want to capture. In our case, we are capturing all data from http://www.reddit.com where the xpath (or nodes that we want to return) is any anchor tag that contains a class of title. If we explore the source code of http://www.reddit.com we can see that each title on the page is indeed an anchor tag with a class of title. At the end of the request the reddit object should now contain the return value from the request or, in other words, the headlines from the Reddit homepage.

Now let's look at the templating script block:

<script type="text/os-template" require="reddit">

<ul>

   <li repeat="${reddit.content.query.results.a}">

      <a href="${Cur.href}">${Cur.content}</a>

   </li>

</ul>

</script>

This is the block that will define the template for displaying our results. To define a templating script block, we define the type to be "text/os-template" and then we can include the object (in our case from the data pipelining request) that we want to make available to the template - we set this to "reddit" - the same value that we set as the key of the data pipelining request.

Now we can simply define the HTML that we want to use, with the variables, to display our results. For this simple use case we'll simply create an unordered list with all of the headlines displayed as anchor tag links. In OpenSocial templating, we can insert the value from a data source by including the variable that we want to act upon, displaying it in the format ${VARIABLE}. For instance, in our data pipe if we defined our key to be "foo" and in the foo object we have a sub-element named "bar", we could display it using ${foo.bar}. Another aspect about templating that we're going to be taking advantage of is repeaters. This will allow us to repeat a block of code for each object available, and is done so by adding a repeat="${OBJECT}" attribute on the block that should be repeated, in this case the <li> tag. This will create a list item for each headline we encounter.

Now, if we look at the HTML block knowing this, we can see that we are creating a root unordered list node, then creating a list item for each headline we encounter in the Reddit headlines object. The headlines are embedded in the object at reddit.content.query.results.a. Within each list item we display an anchor tag. The href of the anchor is set to that of the headline link and the text of the link is set to the headline that we get back from the query.

Once the gadget has rendered you should be presented with a very unstyled unordered list, which you may then apply CSS on to. Using this type of setup with a service like YQL, data pipelining, and templating, you can create gadgets that render very dynamic content while reducing the amount of coding that is needed.

OpenSocial drives apps for the Consumerprise Era!

2011-07-29T18:31:00.000-07:00

OpenSocial rocks! Plain and simple. On Wednesday, Jive Software hosted an event where we showed off the Jive Apps Market. Thirteen of our app partners were present to demonstrate their killer apps (AppFusions, Appirio, Box, Crowd Factory, Gliffy, Lingotek, RoundPegg, Rypple, SalesCrunch, SolutionSet, SurveyGizmo, ThreeWill, yaM Labs). You can learn more about it in different blogs like Forbes and InformationWeek Brainyard, the Twitter stream, and on the Jive Developer Community.

This is the world's first social enterprise apps market. And it's based on OpenSocial. Each application is an OpenSocial gadget that gets rendered inside a user's Jive Apps dashboard.

Why is OpenSocial such a great fit for this? First of all, it gives us an open, industry standard application model that our partners can use to deliver SaaS based capability that extends and compliments the underlying Jive Platform.

OpenSocial also provides access to the enterprise social graph. You can use the programming model to access the members of your company that you are connected with as well as the member of your groups.

And let's not forget the activity stream! Inside of Jive, OpenSocial applications can post activities into the stream, which enables them to spread virally across the enterprise.

Would we have been able to build and deliver the Jive Apps Market as quickly as we did without OpenSocial? No way. By leveraging the OpenSocial, and building on top of Apache Shindig, we were able to leverage the power of the community, appeal to a broad base of fantastic application developers working at innovative companies, and provide enterprises with the security of working with an industry leading open, standard technology.

Posted by Mark Weitzel, President, OpenSocial Foundation & Developer Evangelist, Jive Apps

New OpenSocial Community Groups on Facebook

2011-07-25T13:38:00.000-07:00

Hello Everyone,

This will be a quick update for the OpenSocial community. I wanted to let everyone know that we have two new upcoming avenues for people to reach out to us on Facebook. This will allow us to build more communication channels for those wishing to talk with others who are working with or interested in OpenSocial, or the many open source technologies that it is integrated with.

So, with that said, here are the two new channels on Facebook for to take a look at - a page and a group:

I will be adding and filling in the content on these pages in the coming days so that they are complete. Please feel free to use these channels to engaged with others in the community.