Date Issued: | 10th September, 2018 |
Latest version: | https://www.imsglobal.org/spec/lti-rs/latest/ |
IPR and Distribution Notices
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the specification set forth in this document, and to provide supporting documentation.
IMS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on IMS's procedures with respect to rights in IMS specifications can be found at the IMS Intellectual Property Rights web page: http://www.imsglobal.org/ipr/imsipr_policyFinal.pdf.
Copyright © 2018 IMS Global Learning Consortium. All Rights Reserved.
Use of this specification to develop products or services is governed by the license with IMS found on the IMS website: http://www.imsglobal.org/speclicense.html.
Permission is granted to all parties to use excerpts from this document as needed in producing requests for proposals.
The limited permissions granted above are perpetual and will not be revoked by IMS or its successors or assigns.
THIS SPECIFICATION IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS SPECIFICATION SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER THE CONSORTIUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS SPECIFICATION.
Public contributions, comments and questions can be posted here: www.imsglobal.org/forums/ims-glc-public-forums-and-resources.
© 2018 IMS Global Learning Consortium, Inc.
All Rights Reserved.
Trademark information: http://www.imsglobal.org/copyright.html
Document Name: IMS LTI Resources Search (RS) Service Conformance and Certification v1.0
Revision: 10th September, 2018
The Learning Tools Interoperability (LTI) Resource Search (RS) specification defines how to search digital repositories for a set of resources via a web services API. The standard addresses searching learning object repositories (LORs), and other catalogs of learning resources. The specification supports executing these search from learning tools using various attributes of resources and returning full metadata about the resources to the learning tools. Results can be launched either as URLs or LTI links. The goal of the LTI Resource Search standard is a standard way for students and teachers to be able to search resource providers, such as learning object repositories, from single sources or aggregated from multiple sources, within a learning object consumer such as a learning management system or other educational platform.
This document is the LTI Resource Search Service v1.0 Conformance and Certification document and as such it is used to define how a product can be certified as IMS LTI Resource Search Service 1.0 compliant.
1. Introduction
3. Service Provider Conformance
4. Service Consumer Conformance
5. LTI Resource Search Service Certification
Appendix A Summary of the Conformance Tests for a Service Provider
Appendix B Summary of the Conformance Tests for a Consumer
This document is the LTI Resource Search Service v1.0 Conformance and Certification document and as such it is used to define how a product can be certified as IMS LTI Resource Search Service 1.0 compliant. The formal definition of the LTI Resource Search Service 1.0 is supplied in the following documents:
This document is released for public adoption and implementation of the LTI Resource Search Service 1.0 specification. Public contributions, feedback on adoption of the specification, comments and questions can be posted at: www.imsglobal.org/forums/ims-glc-public-forums-and-resources.
All sections marked as non-normative, all authoring guidelines, diagrams (with the exception of the UML diagrams), examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119]. This means that from the perspective of conformance:
The Conformance and Certification Guide for this specification may introduce greater normative constraints than those defined here for specific service or implementation categories.
The SHOULD/SHOULD NOT/RECOMMENDED statements MUST NOT be used in any document, or section of a document, that is responsible for defining the information model and/or the associated bindings and/or conformance and certification.
The structure of the rest of this document is:
2. The Conformance Process | The formal process to be undertaken by a vendor wishing to obtain LTI Resource Search Service conformance certification; |
3. Service Provider Conformance | The conformance requirements that must be achieved for the certification of a LTI Resource Search service provider; |
4. Service Consumer Conformance | The conformance requirements that must be achieved for the certification of a LTI Resource Search service consumer; |
5. LTI Resource Search Service Certification | A comparison of the endpoint certification requirments for a service provider and a service consumer. |
References | The set of references cited throughout this document; |
Appendix A Summary of the Conformance Tests for a Service Provider | A summary of the set of tests that will be applied to a Service Provider to confirm that an implementation is compliant; |
Appendix B Summary of the Conformance Tests for a Consumer | A summary of the set of tests that will be applied to a Consumer to confirm that an implementation is compliant. |
API | Application Programming Interface |
AfAPNP | Access for All Personal Needs and Preferences |
CASE | Competencies and Academic Standards Exchange |
HTTP | Hypertext Transfer Protocol |
I-BAT | IMS Binding Autogeneration Toolkit |
IETF | Internet Engineering Task Force |
ISO | International Standards Organization |
IUT | Implementation Under Test |
JSON | Java Script Object Notation |
LOR | Learning Object Repository |
LTI | Learning Tools Interoperability |
OAS | OpenAPI Specification |
PNP | Personal Needs and Preferences |
REST | Representation State Transfer |
RFC | Request for Comments |
RS | LTI Resource Search |
TLS | Transport Layer Security |
UML | Unified Modeling Language |
URI | Uniform Resource Identifier |
URL | Uniform Resource Locator |
YAML | Yet Another Markup Language |
This Section is NOT NORMATIVE.
The process for conformance testing implementations of LTI Resource Search Service includes the following:
All of the REQUIRED feature tests MUST be passed successfully to be considered IMS LTI Resource Search Service compliant. If a system is to be certified for any of the OPTIONAL features then the corresponding tests for these MUST ALSO be passed. When using the conformance test systems you are required to identify which optional features are supported by the implementation under test. The conformance test systems will then test ALL of the REQUIRED and identified OPTIONAL features to confirm their correct implementation. The IMS Product Certification directory will then identify the set of optional features that are certified as being compliant.
After you have submitted your successful conformance information to conformance@imsglobal.org, and received confirmation and a registration number from IMS Global you may then apply the appropriate conformance mark. The IMS Global conformance chart will list your conformance details. If you have any questions, please feel free to contact us at any point.
Membership in the LTI Resource Search Service Alliance is the only way to achieve official conformance to the LTI Resource Search Service standard. Products without a IMS conformance Registration Number are not considered to be compliant by IMS Global.
This Section is NORMATIVE.
In Table 3.1 the following should be noted:
The set of endpoints that MUST be supported by a Service Provider is listed in Table 3.1.
Service Call | Endpoint | HTTP Verb | Mode |
---|---|---|---|
searchForResources | /resources | GET | Resp |
getAllSubjects | /subjects | GET | Resp |
The functional capabilities of such systems are:
The Conformance Test System used to certify an LTI Resource Search 1.0 Service Provider is available at: http://validate.imsglobal.org/RSv1p0_CTS_ServiceProvider/index.html.
A summary of the set of tests that will be used to determine the compliance of an implementation of the service provider functionality is given in Appendix A.
This Section is NORMATIVE.
In Tables 4.1 and 4.2, the following should be noted:
The set of endpoints that MUST be supported by a Service Consumer is listed in Table 4.1.
Service Call | Endpoint | HTTP Verb | Mode |
---|---|---|---|
searchForResources | /resources | GET | Init |
The set of endpoints that MAY be supported by a Service Consumer is listed in Table 4.2.
Service Call | Endpoint | HTTP Verb | Mode |
---|---|---|---|
getAllSubjects | /subjects | GET | Init |
The functional capabilities of such systems are:
NOTE: From a conformance perspective, 'handle' means that the consumer must store the data in a persistent manner and must demonstrate that storage. Conceptually, if a read request was made to the service consumer for that record then all of the data supplied by the service provider should be recovered.
The Conformance Test System used to certify a LTI Resource Search 1.0 Service Consumer is available at: https://onerostervalidator.imsglobal.org:8443/ltirs-client-cts-webapp/index.
A summary of the set of tests that will be used to determine the compliance of an implementation of the consumer functionality is given in Appendix B.
This Section is NORMATIVE.
A system that successfully achieves LTI Resource Search Service certification will have a certain set of functional capabilities. LTI Resource Search Service certification does NOT guarantee interoperability for ALL features between ALL other LTI Resource Search Service compliant solutions. The set of functional properties that a LTI Resource Search Service certified product may have is shown in Table 5.1.
Service Call | Endpoint | Provider | Consumer |
---|---|---|---|
searchForResources | /resources | Required | Required |
getAllSubjects | /subjects | Required | Optional |
The key points to note from Table 5.1 are:
[CASE, 17] | Competencies and Academic Standards Exchange (CASE) Service, B.Grogan, G.Nadeau, C.Smythe and J.Hobson, IMS Global Learning Consortium Inc., July 2017, https://www.imsglobal.org/sites/default/files/CASE/casev1p0/information_model/caseservicev1p0_infomodelv1p0.html. |
[I-BAT, 06] | IMS Binding Auto-generation Toolkit (I-BAT), C.Smythe, IMS Global Learning Consortium Inc., July 2006. |
[ISO 8601] | ISO8601:2004 Data elements and interchange formats - Information interchange - Representation of dates and times, ISO, International Standards Organization (ISO), 2000. |
[RFC 2119] | Key words for use in RFCs to Indicate Requirement Levels., S. Bradner, IETF (RFC 2119), March 1997, https://tools.ietf.org/html/rfc2119. |
[RFC 3066] | Tags for the Identification of Languages, H.Alvestrand, IETF (RFC 3066), January 2001, https://www.ietf.org/rfc/rfc3066.txt. |
[RS-BP, 18] | IMS LTI Resources Search Service 1.0 Implementation Guide Final Release, A.Blum, T.Ingram, V.Jaiswal, and J.Hobson, IMS Global Learning Consortium Inc., September 2018, https://www.imsglobal.org/lti-rs/v1p0/impl. |
[RS-CC, 18] | IMS LTI Resources Search Service 1.0 Conformance and Certification Final Release, A.Blum, T.Ingram, V.Jaiswal, and C.Smythe, IMS Global Learning Consortium Inc., September 2018, https://www.imsglobal.org/spec/lti-rs/v1p0/cert. |
[RS-OA, 18] | IMS LTI Resources Search (RS) Service 1.0 OpenAPI Definition Final Release, A.Blum, T.Ingram, V.Jaiswal, and C.Smythe, IMS Global Learning Consortium Inc., September 2018, https://www.imsglobal.org/spec/lti-rs/v1p0/openapi_doc. |
[RS-RJ, 18] | IMS LTI Resources Search Service 1.0 REST/JSON Final Release, A.Blum, T.Ingram, V.Jaiswal, and C.Smythe, IMS Global Learning Consortium Inc., September 2018, https://www.imsglobal.org/spec/lti-rs/v1p0/restbind. |
[RS-SM, 18] | IMS LTI Resources Search Service 1.0 Service Model Final Release, A.Blum, T.Ingram and C.Smythe, IMS Global Learning Consortium Inc., September 2018, https://www.imsglobal.org/spec/lti-rs/v1p0/infomodel. |
[UNICODE, 16] | UNICODE Collation Algorithm Version 9.0, M.Davis, K.Whistler and M.Scheer, Unicode Technical Standard #10, May 2016. |
The set of tests that will be used to determine if an implementation of the service provider functionality is compliant are summarised in Table A1. The features supplied Table A1 are:
ID | Mode | Description |
---|---|---|
101 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'search' (using the phrase search!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
102 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'name' (using the phrase name!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
103 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'publisher' (using the phrase publisher!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
104 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningResourceType' (using the phrase learningResourceType!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
105 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'subject' (using the phrase subject!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
106 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'description'. The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
107 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'language' (using the phrase language!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
108 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'typicalAgeRange' (using the phrase typicalAgeRange!='12'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
109a | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'textComplexity' (using the phrase textComplexity.name!='DRA'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
109b | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'textComplexity' (using the phrase textComplexity.value!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110a | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.alignmentType!='assesses'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110b | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.educationalFramework!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110c | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.targetDescription!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110d | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.targetName!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110e | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.targetURL!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110f | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.caseItemURI!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
110g | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'learningObjectives' (using the phrase learningObjectives.caseItemGUID!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
111 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'publishDate' (using the phrase publishDate!='1999-12-31'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
112 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'author' (using the phrase author!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
113 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'timeRequired' (using the phrase timeRequired!='PT1H'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
114 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'technicalFormat' (using the phrase technicalFormat!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
115 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'educationalAudience' (using the phrase educationalAudience!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
116 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'rating' (using the phrase rating!='1'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
117 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'accessibilityAPI' (using the phrase accessibilityAPI!='ARIAv1'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
118 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'accessibilityInputMethods' (using the phrase accessibilityInputMethods!='fullMouseControl'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
119 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for the search term 'accessMode' (using the phrase accessMode!='tactile'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
121 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using equal ('=' using the term 'name'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
122 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using not equal ('!=' using the term 'name'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
123 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using greater than ('>' using the term 'publishDate'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
124 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using greater than or equal ('>=' using the term 'rating'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
125 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using lesser than (' <' using the term 'publishDate'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
126 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using lesser than or equal ('>=' using the term 'rating'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
127 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using contains ('~' using the term 'subject'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
131 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the AND predicate (using the phrase 'rating!= AND subject~'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
132 | Req | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the OR predicate (using the phrase 'name= OR rating=5'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
151 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the pagination query parameters ?limit and ?offset (using the phrase name!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
161 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the sort query parameter ?sort (using the phrase &sort=name). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
162 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the sort and orderBy (ascending) query parameters (using the phrase ?sort=learningResourceType&orderBy=asc on a filter of name). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
163 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using the sort and orderBy (descending) query parameters (using the phrase ?sort=learningResourceType&orderBy=desc on a filter of name). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
171 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using a single field (name) selection query parameter ?fields (using the phrase name!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
172 | Opt | To confirm the service provider's '.../ims/rs/v1p0/resources' endpoint works correctly for searches using three fields (description, subject, learningResourceType) selection query parameter ?fields (using the phrase name!='NULL'). The test system issues the searchForResources request and expects to receive a fully populated JSON payload. |
301 | Req | To confirm the service provider's '.../ims/rs/v1p0/subjects' endpoint works correctly. The test system issues the getAllSubjects request and expects to receive a fully populated JSON payload. |
The set of tests that will be used to determine if an implementation of the consumer functionality is compliant are summarised in Table B1. The features supplied in Table B1 are:
ID | Mode | Description |
---|---|---|
1.1 | Req | Confirm that the consumer makes requests using valid access token usage as per OAuth 2.0; |
2.1 | Req | Confirm that the consumer makes valid requests for obtaining all subjects using the endpoint '.../ims/rs/v1p0/subjects'; |
2.2 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' (a valid 'filter' URL query parameter must be supplied); |
3.1 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'limit' URL query parameter; |
3.2 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'offset' URL query parameter; |
3.3 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'filter' URL query parameter; |
3.4 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'sort' URL query parameter; |
3.5 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'orderBy' URL query parameter; |
3.6 | Req | Confirm that the consumer makes valid requests for obtaining all resources using the endpoint '.../ims/rs/v1p0/resources' with a valid 'fields' URL query parameter. |
Title: | IMS LTI Resources Search (RS) Service Conformance and Certification v1.0 |
Editors: | Colin Smythe, IMS Global (UK) Jill Hobson, IMS Global (USA) |
Co-chairs: | Adam Blum, OpenEd (USA) Tom Ingram, Escambia County School District (USA) |
Version: | 1.0 |
Version Date: | 10th September, 2018 |
Status: | IMS Final Release |
Summary: | The IMS LTI Resource Search (RS) Service defines how to search digital repositories for a set of resources. The standard addresses searching learning object repositories (LORs), and other catalogs of learning resources, from learning tools using various attributes of resources and returning full metadata about the resources to the learning tools. Results include resource access specification as either URLs or LTI links. The benefit for an educator or student using the learning tool (such as a Learning Management System) is seamless ability to search resource libraries for appropriate resources and transparent launching of those resources. This document contains the conformance and certification requirements and processes for the LTI Resource Search service certification. |
Revision Information: | First release of this specification. |
Purpose: | For public adoption. |
Document Location: | IMS Public Website (Specifications Download): https://www.imsglobal.org/specifications.html |
The following individuals contributed to the development of this document:
Ray Baranoski | Safari Montage (USA) |
Adam Blum | Open Ed (USA) |
Stacy Cohen | Framingham State University (USA) |
Paul DeVey | Pearson (USA) |
Viktor Haag | D2L Corporation (Canada) |
Mark Hannah | Knovation (USA) |
Jill Hobson | IMS Global (USA) |
Tom Ingram | Escambia County School District (USA) |
Vikash Jaiswal | Knovation (USA) |
Joshua Marks | PCG (USA) |
Justin Mason | University of Wisconsin Extension (USA) |
Elizabeth Neuman | State of Wisconsin Dept. of Public Instruction (USA) |
Colin Smythe | IMS Global (UK) |
Version No. | Release Date | Comments |
---|---|---|
Final Release 1.0 | 10th September, 2018 | The first formal release for the specification. This specification is made available for public adoption. |
IMS Global Learning Consortium, Inc. ("IMS Global") is publishing the information contained in this document ("Specification") for purposes of scientific, experimental, and scholarly collaboration only.
IMS Global makes no warranty or representation regarding the accuracy or completeness of the Specification.
This material is provided on an "As Is" and "As Available" basis.
The Specification is at all times subject to change and revision without notice.
It is your sole responsibility to evaluate the usefulness, accuracy, and completeness of the Specification as it relates to you.
IMS Global would appreciate receiving your comments and suggestions.
Please contact IMS Global through our website at http://www.imsglobal.org.
Please refer to Document Name: IMS LTI Resources Search (RS) Service Conformance and Certification v1.0
Date: 10th September, 2018