IMS Learning Tools Interoperability

Stephen Downes: Half an Hour

Along with the sopecification design has been the development of code. So I've been writing code for a year and a half. But writing code helps me understand what the problems are. It's the practical security for REST. demo - 8 line common cartridge with LTI Basic LTI + CC - sample code - all available [link] (awesome) demo - a bunch of CC - LTI stuff from the tool. Another blog-summary from the IMS conference.

Tools 109

Questions from students at Vancouver Island University

Stephen Downes: Half an Hour

The word 'responsible' is one of those code-words that hides a whole range of preferred behaviours, from respecting copyright to keeping the language clean to refraining from bullying and hurtful behaviour to staying on topic, sitting up, and paying attention. You might be able to teach a person more quickly how to write a REST interface by giving them sample code and describing what to do - this is the ' worked examples ' model.

Developer workshop - CCv1.1 and basic LTI v1.0

Stephen Downes: Half an Hour

Curriculum metadata identifies learning objectives, addressed by a resource (samples of roles, curriculum metadata shown). Join the developers network (free): [link] We talk about code & move code around, but not about the spec itself. The basic LTI security model is based on OAuth. The tool decides the level of security. It may require all the security values, or none of them. The security is separately established between tool and LMS.

eBook 122