What is LTI?

preview_player
Показать описание
Рекомендации по теме
Комментарии
Автор

What a fantastic resource, thank you for putting this together I found it useful!

georgerobinson
Автор

Hi Claude, many thanks for a very informative video. Can I as what you are using to generate the graphics for this video, please?

rickpalmer
Автор

Thanks, great video series! Very helpful for those who just started LTI 1.3 development.


Just a question about deep linking; in the basic LTI we are able to map a tool provider content to an LMS resource via LtiResourceLinkId. Is Deep Linking extension in LTI Advantage providing the same functionality just in separate service or am I missing something?


Thank you again, excited to see more videos!

orhunk
Автор

Hello Claude,
I've one question regarding the deep linking implementation. as per my understanding, once the user selects the deep link content item on the tool's content selection page, there will be a response sent to the deep_link_return_url thats received in the launch (for CreateDeepLink) request. We are planning to implement this endpoint as a separate process but wondering how will we there come to know that the response received is from which tool. Because as per the specs, the incoming response message has only one parameter in response i.e JWT which is a signed JWT message. to verify the signature of this signed JWT, we will need the tool's public key, for which we need to know which tool has sent this response. I checked if we have any identifier for Client_id in the incoming request headers but didn't get any such header there which will tell about the tool's identity. Can you please let us know how do we implement this? Do we need to maintain the tool's identifier at the time of initial OIDC or launch itself in local context and then use the same tool's id for getting it's public key, because there we know which tool we are initiating the request to?

kishorsmarathe
Автор

Hello Claude,
We are in the intermediate stage of LTI 1.3 implementation (Platform side) and able to launch a resource as LTI 1.3 claims payload standards. I'm working on enhancing the same to have Assignment and Grading service where in the usage of line items is mandatory for pushing grades from tool back to platform. However, the specs mention that one Resource link can have more than line items. at the time of launching a resource link, if there are more than one line items, then in the endpoint claim we should pass lineitems.url, to which the tool will query and then it will basically get the gradable line item. How will the tool decide which line item is gradable and which isn't. Ideally, even if there are more than one line items, only one line item is going to be associated with the resource link's gradebook. is this understanding correct? Appreciate your help so far and looking forward to your response

kishorsmarathe
Автор

hi Claude, Will you be able to share the list of jar files that we would need in order to support LTI 1.3 implementation. The plan is to migrade to LTI 1.3 from LTI 1.1

kishorsmarathe
Автор

Ok, do you have any samples of LTI Courses? how the final course content package will look like? I tried searching a lot, but not getting anything from anywhere. Any help is appreciated!

NimodNamboodiri
Автор

Sounds like an aicc course, having a difficult time understanding what is the added value of LTI over existing standard like aicc/scorm/xapi

lilianne
Автор

hi sir do you have guide how to implement LTI to LMS?

zulfarismazlan