Working Session - Palo Alto - March 30 3pm - 8pm
We'll have an OpenSocial 2.0 working session at the Jive Offices in Palo Alto, California, March 30, 2011 from 3:00pm - 8:00pm PST.
Where
Jive Software
325 Lytton Avenue, Suite 200, Palo Alto, CA 94301
On-street parking is available, or the nearest Caltrain station is only a few blocks away.
Pizza & Beverages will be provided!
Agenda
The objective is to
1) Review current proposals
- ActivityStreams approach and come to a consensus on extension location
- agree that action links should be supported
- point to osapi.http (should be this type of request)
- should support HTTP verbs
- base JSON specification is what we want to support. We need to get this locked down.
- *** deliverable tonight: path for this section
- JSON structure should have a label, what to do with it (GET URL) and a hint on how to handle the link (new page / load in app / etc)
- HTTP request API should include 2XX and 3XX HTTP response ranges (OPEN BUG FOR THIS).
- *** look into the embedded experience proposal
- ActionLink proposal:
org.os
actionLink: //JSON object containing list of action links
embExp: //context that the action link should be loaded into (e.g. embedded experience, view name, etc.)
- Activity Streams spec (and our implementation) should not include cc, bto or bcc. We should only include cc in our implementation. cc should include an array of OS global IDs.
- *** define what we want an Activity Streams object with OS namespace to look like (write spec)
- App Data
1. No dataContext because it's transient
2. Deprecate hidden userPrefs
3. Clarify use of userPrefs / Define pref view / recommend how to use view
4. Make userPrefs a robust API
4.1. Define scopes: User / group / user write app read / global to app
- makeRequest deprecation
1. Remove gadgets.io completely
2. Need to speak with Paul
- global id. using @ instead of : currently we will stick with : until we understand the context of why we use a colon instead of at @ sign.
2) Author relevant sections of the spec.