There are some compliance tests https://svn.apache.org/repos/asf/shindig/trunk/content/gadgets/compliance/ https://svn.apache.org/repos/asf/shindig/trunk/content/gadgets/compliance-1.0/ but I have never run them, I am sure they are out of date.
On Thu, Feb 13, 2014 at 11:55 AM, Stanton Sievers <ssiev...@apache.org> wrote: > I think in general we need to update our compliance tests to help avoid > issues like this in the future. > > Does anyone know of any tools that can help to do this? I'm wondering how > other projects that are tied to a spec handle spec compliance. > > -Stanton > > > On Thu, Feb 13, 2014 at 11:14 AM, Andreas Kohn <andreas.k...@gmail.com>wrote: > >> Hi, >> >> On Wed, Feb 12, 2014 at 7:18 PM, Ryan Baxter <rbaxte...@apache.org> wrote: >> >> > On Tue, Feb 11, 2014 at 12:57 PM, Andreas Kohn <andreas.k...@gmail.com> >> > wrote: >> > > 1. Change the MediaItems request parameters to match opensocial: >> > currently >> > > shindig expects the media item id in the 'mediaItemId' parameter, but >> > > OpenSocial says it should be in the 'id' parameter instead. This change >> > > would break the *RPC* API, the REST API would be unaffected. It could >> be >> > > made to be compatible though by checking both parameter names. >> > >> >> >> > I like the solution of support both, and I am fine with that. Would >> > the MediaItem interface change? >> >> >> No, it only changes the names of the parameters expected in the RPC calls >> (it actually affects two, >> but both can be made to be handled backwards-compatibly.) >> >> Working on finalizing the parts 1 and 3, hopefully should have some code to >> show tomorrow or Monday. Keeping the change >> for 2 locally is fine for me, as long as we can get those incompatibilities >> between the OpenSocial standard >> and Shindig out eventually. >> >> Regards, >> -- >> Andreas >>
