Basic LTI – part I

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.

First of all there are a lot of different language implementations for creating bLTI tools, for instance Java, PHP and Python from the IMS-DEV opensource repository. As our B2 tools are created in Java with integrated Javascript it seems like good opportunity to investigate the Java Tool Provider implementation to see how easy/difficult it is to “translate” them (especially the content plugin I currently work on) into bLTI. With the alternatives that would include translating the code to a web centric code, i.e. to pure javascript.

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).

 

This entry was posted in Plugin development and tagged . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *