On Thu, Nov 08, 2007 at 08:05:55AM +0000, Julian Bond wrote: > > Paul Lindner <[EMAIL PROTECTED]> Wed, 7 Nov 2007 17:45:15 > >Please see our latest announcement here regarding the hi5 developer > >sandbox and the release of our javascript glue code. > > Congratulations! I noted this: "We also do not support the RESTful API > at all. We plan to skip AuthSub and move straight to OAuth > authentication. Furthermore our API server does not support the URL > layout of the OpenSocial Data API." > > - Skipping AuthSb and going straight to oAuth. Do you think Google and > other Containers will do the same?
Taking a gamble here. We want to implement OAuth/OpenID, period. So hopefully providing such an implementation can move the standard in the right direction. Remember the adage "Rough consensus and working code" > - URL Layout. If we're going to have common data APIs across containers > do/should we all use the same URL layout? Or do we have to start > thinking about another layer of indirection and end point > auto-discovery? Actually, it's the placement of URL params inside the URI that is troublesome. URIs like: http://foo.com/rest/user/12345/friends/start=1/end=200?filter=NEW do not fit the Verb/Noun/ProperNoun + Adjectives model Enunciate provides. The planned way to fix this is to add a URI pattern that will allow adjectives to be provided from the URI. As far as auto-discovery? Why reinvent the wheel. Either add link rel= tags in the user profile or extend RSD. > Same question again; Are there any real world examples of Data API > output? I'm not sure, but I thought someone mentioned Orkut supported some calls. -- Paul Lindner hi5 Architect [EMAIL PROTECTED]
pgpRK8rFe60ZT.pgp
Description: PGP signature
