UserPrefs vs AppData

Mark Weitzel

No one has signed up yet so, for now, I'll throw my name in the hat. From an IBM perspective, we've been looking at a number of use cases around user prefs & app data and would like to help drive this work.

Y

Y

Merge-incorporate Activity Streams into OpenSocial

Mark Weitzel / Eric Woods

There is a patch submitted to the SVN for the spec and the code is available in the Shindig sandbox. There are several issues with this work that we are tracking down:

• The ActivityStrea.ms effort has not released a stable version of their specification
• We need to ensure there is proper IP coverage and clarity around anything that the AS team produces

Y/Y

Y/Y

Investigate spec changes to support inline gadgets

Mark Weitzel / Rich Manalang

(live) Inline gadget discussion thread
(deprecated) Inline gadget discussion thread

...(From EOS) This is a general requirement to satisfy the performance requirements found within enterprise settings.

Y

Y

Add semantic information to relationships

Mark Weitzel / Inbal Ronen (IBM) / Ido Guy (IBM)

...

Y/N/N

Y/?/?

Align CMIS and OpenSocial

Mark Weitzel / Eric Woods / Matt Tucker / Bill Lynch

...

Y / Y / ? /?

Y / Y / ? /?

Formalize Javascript Container APIs

Michael Hermanto

Common Container Specification

? /?

? /?

Add semantic information to relationships

Mark Weitzel / Inbal Ronen (IBM) / Ido Guy (IBM)

...

Y/N/N

Y

Make JSON-RPC a MUST instead of a MAY

XSD Validation & ATOM Mapping (or RelaxNG)

Mark Weitzel

We need to determine the right extension patterns for the various OpenSocial schema. Also, there was a blog post on OpenSocial's mapping to ATOM that is worth discussing.

Y

Y

Add additional lifecycle events and/or new management callbacks

Mark Weitzel

This could be the start of a "Management Extension" for OpenSocial

Y

Y

Add appInvite to OSML.

Mark Weitzel / Chris Cole

This idea came up in the mobile discussion adding mobile views . We already have the script function "requestShareApp" and 
<os:PeopleSelector>. Perhaps a better approach could be to extend 
OSML to have a simple tag-based invite UI. 
<os:AppInvite /> 
Then the container could choose the appropriate implementation, be it 
a link/URL or a rich dialog.

Y

Y

Improvements to Tabs/Skins

Mark Weitzel

Improvements to Tabs and Skins

Y

Y

Selection and Action Contribution

Andrew Davis/Matt Hatem

Declarative Actions Contributions and Selection

Y

Y

OpenSearch

Andrew Davis/Igor Belakovskiy

Y

Container Window/Dialogs

Andrew Davis/Chih-hung Chiang

Y

Embedded Experiences

Ryan Baxter

Embedded Experiences

Y

Y

Remove Quirks mode

Matt Marum

Remove Quirks Mode

Spaces Proposal

Evgeny Bogdanov

Groups Discussion
Vote for inclusion in scope here.
Issue with patches here

View Level Feature Proposal

Matt Marum

View Level Features Proposal

Simple Gadget Format Proposal

Chris Cole

Simple Gadget Thread
Issue 1162 for patch
Vote: Revision 1371

Y

Y

http://docs.opensocial.org/display/OSD/Gadget+Manifest+FileGadget Manifest

Chris Cole

Manifest Proposal
Manifest Thread

Potentially the use cases could be covered by the "View Level Features" proposal, provided the use cases are fleshed out and covered.

This proposal has been abandoned for this spec cycle.  Greater interop is required before this has enough value to justify the work.

Y

Y

oEmbed Integration

Paul Lindner

Define how gadgets can be referenced in oEmbed.

Y

Y

oStatus Integration

Paul Lindner

Adding well-known and webfinger support, extend activity streams with magic signatures and salmn

Y

Y

OAuth 2 Integration

Paul Lindner

Document and specify that the current securityToken scheme is really OAuth2 Bearer Tokens

Y

Y

Content Type URL signable

Bastian Hofmann

Cross Container Data Requests

Chris Cole

Discussion Thread

Issue 1181
VOTE Revision 1418

Defines a mechanism for using data tags to invoke social API calls from a different container and a way to embed multiple credential sets in a gadget for a variety of APIs running on different provider sites.

Y

Y

Remove "Non-Tags" section from Social Gadget spec

Chris Cole

The "Non-Tags" section is not necessary since any additions to the spec must be approved through the spec process anyway.  It should be removed to avoid confusion.
Discussion thread
Non-Tags spec section
Issue 1179
Vote: Revision 1411

Y

Y

Standardize variable substitution on EL syntax and consolidate EL spec definitions

Chris Cole

Discussion Thread
Older Variable substitution is more limited and redundant to EL syntax.  Spec should standardize on EL syntax and deprecate older variable syntax
Issue 1164
*[VOTE Revision 1371

Y

Y