This link has been bookmarked by 8 people . It was first bookmarked on 02 Jul 2008, by Charles Nelson.
-
07 Jul 09
-
28 Mar 09
-
08 Oct 08
-
So we threw away the Sakai rule book, and embraced a different development strategy. This strategy, feeding on the pace of innovation in OpenSocial and its reference implementation Apache Shindig, has enable us to transform the Sakai interface. A UI layer developed by UI designers and developers in pure Javascript and HTML is connected to Sakai using pure HTTP protocols with a minimal layer of REST semantics.
-
Underneath, it is Sakai, operating as a data server, but ontop it is Gadgets, Widgets and Ajax applications delivered in HTML. We call this SData, where many of the concepts are borrowed from GData and other Google API’s.
Meanwhile the OpenSocial specification is evolving; version 0.8 has introduced the idea of Groups. The focus of protocol development has moved away from ATOM and towards a simpler, and more browser efficient REST based JSON API
-
-
21 Jul 08
hansdezwart"The monolithic application in teaching and learning and research has died." Onze oplossing kunnen niet meer éénvormig en groot zijn.... "small pieces, loosely joined" - Wat doen wij daaraan?
-
05 Jul 08
paul reidIf we, in delivering applications for education create barriers to entry that prevent that army of developers from engaging we will lose the benefit of the powerhouse that is represented by the open source development community.
-
02 Jul 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.