The content-item message is used to provide a mechanism for users to interact with a Tool Provider (TP) in the process of selecting one or more content items for insertion into the tool consumer. A typical use case would be to allow a user within a Tool Consumer (TC) to click a button on the toolbar of a text box editor, which opens a TP within an iframe (or pop-up window), use the interface provided to select one or more items, and have the selected item(s) returned to the TC and inserted into the text box. This may be an instructor adding content to a content page, or could be a student selecting an attachment to submit as part of an assignment.
Different types of content item are supported for selection using this message:
- a customized launch of the TP;
- a static HTML hyperlink;
- an embedded image or other media type;
- embedded HTML;
- an iframe;
- a file (to be stored within the TC).
Since this message allows users to interact with the TP when creating LTI launch links, it can also be used to improve the workflow when adding an LTI link for TPs which require custom parameters to be included in the launch; these custom parameters can be specified when the link is created based on the content item selected by the user.
[HTTP, 14] Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content , R. Fielding et al. Retrieved 24 May 2016 from http://tools.ietf.org/html/rfc7231
[LTI, 12] G.McFall, L.Neumann, S.Vickers, IMS Global Basic Learning Tools Interoperability v1.1.1, IMS Global Learning Consortium, September 2012. http://www.imsglobal.org/lti/.
[LTI, 14 OM] S.Vickers, Outcomes Management v2.0, IMS Global Learning Consortium, December 2014. http://www.imsglobal.org/lti/.
[CIa, 15] S Vickers, Content-Item Message, IMS Global Learning Consortium, May 2016. http://www.imsglobal.org/lti/.
[CIb, 15] S Vickers, Content Items in the application/vnd.ims.lti.v1.contentitems+json format, IMS Global Learning Consortium, May 2016. http://www.imsglobal.org/lti/.
[OAuth, 10] The OAuth 1.0 Protocol, E. Hammer-Lahav. Retrieved 24 May 2016 from http://tools.ietf.org/html/rfc5849