I’ve started investigate the IMS Basic LTI (bLTI) widget possibilities for DEVELOP.
Like Wookie, Google Widgets and any other widget framework, bLTI needs a server, in IMS terms called a Tool Provider, for the Tool Consumer, which in our case is Blackboard but could be any service with a bLTI integrated placeholder. I have in numerous places discussed the drawback of relying on a separate institutionally run server (e.g. in this post and some JISC reports), so won’t elaborate on that here, but focus on the advantages of using bLTI (for our project) instead of an alternative such as Google API or Wookie API.
Secondly all the major LMS’es in use in HE (e.g. Blackboard, Moodle, Sakai) have bLTI tool consumer placeholders, so the resulting code would be usable within all of these LMS’es, provided obviously that the institutions run tool provider servers (the main advantage of using Netvibes/Google API).