Alex Balleste spent the last two weeks at the Unviersity of Michigan working with me on IMS Tool Interoperability. We got a lot done including:

• We have developed a REST profile for IMS TI 1.0
• We have developed extensions that allows the TI Proxy tool to do configuration and permission setting for the tool and have added it to the Deployment Descriptor and to the LaunchRequest.
• We have extended the Sakai IMS-TI JSR-168 portlet that supports all of the launch descriptors including the original, SOAP Lite, and REST as well as the Authz and Config extensions – this interoperates with 1.0 compliant placements as well. This portlet works in Sakai and any other JSR-168 compliant portal.
• We have developed sample tools supporting the IMS TI REST profile that are written in Java, Ruby, and PHP.