...
We'll make as much progress as we can with the following, but I expect that we will not make it through all of the topics.
Specifications Issues and cleanup:
...
There should be better links to filter and get concise view of the v2.0 issues and pending votes. The following provides a view of all of the 2.0 issues:
It would be nice if we could figure out how to view only the current proposals open for vote. If anyone has ideas here chime in.
AppData
...
Cross Container Requests
...
CMIS proposal
...
General discussion and thoughts about scoping but nothing concrete. This will be added to future agenda
...
Cross Container Requests
...
There was some confusion on the use cases where the community started vs. where we ended up from a recommendation perspective. There were several threads as part of that discussion:
- Managing multiple service providers
- Supporting other types of authorization
- Consistency with Gadget Registration
- Portability/Configuration across development/test/production
- ....
We took the to do to go back and make sure we document all of the use cases with the community (3/18).
...
OAuth 2
...
Discussion points:
- Specification changes required to maintain backward compatability with OAuth 1.0a
- Talked about Open Source options to provide OAuth 2.0 support (Apache Amber as one future possibility - David will investigate)
We'll revisit more details on this next week
...
Attendees
...
Matt Marum
David Robinson
Eric Woods
Mark Weitzel
Andy Smith
Next Agenda (3/18) & Readout
We spent a bit of time getting ourselves organized and reviewing spec issues. We'll revisit some of these items next week...
Items up for discussion (3/18)
...
Open Issues for actual bugs XSD & API inconsistencies (Matt has identified a few of these with the features and c
Open a bug in shindig for feature version support
Open a bug to manage version compatibility to REST API (http://code.google.com/p/opensocial-resources/issues/detail?id=1146 )
- Need to agree on the best way to manage versions and backward compatibility
Open Feature to support specifying timeout for individual (osapi.http requests). This is managed at the container level today.
- API changes vs Spec changes
IE8 Issue specific header in the response (Optional Params on the HTTP request)
- Need more Details
Alias (Relative URLs) for OSAPI
OAuth
Cross container requests
...