[Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

classic Classic list List threaded Threaded
8 messages Options
Dr. Chuck Dr. Chuck
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Hi all,

I just wanted to share that (a) IMS LTI 2.0 is final, and (b) Sakai-10 is the first officially certified LTI 2.0 Tool Consumer.

/Chuck

Begin forwarded message:

From: Charles Severance <[hidden email]>
Subject: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)
Date: February 12, 2014 at 3:02:28 PM EST
To: IMS LTI Certification submission <[hidden email]>
Cc: Charles Severance <[hidden email]>

Tests for: Sakai-10 (Alpha)

Ref: 9c4b2b44-fd14-442f-9962-6f1f71163848 for University of Michigan

I am submitting my results from the certification tests for your approval.

I have passed the certification tests for the following releases of LTI and wish to apply for certification:

  1. 2.0
  2. Outcomes

Other comments:

Awesome technical support!

Confirmation statement

I confirm that the test results generated are an accurate representation of a properly executed certification testing process. I also confirm that I am familiar with the LTI specification and I am not aware of any circumstances when my application would fail the tests undertaken or fail to comply with any untested requirements of the specification.

Test results

TestRequired forStatus
1: Tool Registration 
1.1: The contents of the registration request are valid2.0Pass
1.2: Invalid tool proxy is rejected2.0Pass
1.3: Valid tool proxy is accepted2.0Pass
2: Protocol Compliance and Resource Information 
2.1: All launch messages have required parameters1.0, 1.1, 1.1.1, 1.2, 2.0Pass
2.2: Sends resource_link_title1.0, 1.1, 1.1.1, 1.2Pass
2.3: Sends resource_link_description1.0, 1.1, 1.1.1, 1.2OK
2.4: Sends tool_consumer_info_product_family_code1.1, 1.1.1, 1.2Pass
2.5: Sends tool_consumer_info_version1.1, 1.1.1, 1.2Pass
2.6: All messages have a recognised message type1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3: OAuth and Signing Requests 
3.1: Sign with agreed consumer key and secret1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.2: Can sign requests with URL parameters1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.3: Can sign a request with a URL parameter with space in the value parameter1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.4: Must include oauth_callback for OAuth 1.0A compliance1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.5: Parameters are encoded using UTF-81.0, 1.1, 1.1.1, 1.2, 2.0Pass
4: Custom Field Support 
4.1: Can send custom fields1.0, 1.1, 1.1.1, 1.2Pass
4.2: Properly maps special characters and case in custom fields1.0, 1.1, 1.1.1, 1.2ToDo
4.3: Supports $User.id substitution variable1.2Pass
4.4: Supports $User.username substitution variable1.2Pass
4.5: Supports $ToolConsumerProfile.url substitution variable1.2, 2.0Pass
4.6: Supports Tool Settings substitution variables2.0Pass
5: User Information 
5.1: Sends a user_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.2: Sends Learner role1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.3: Sends Instructor role1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.4: Follows role naming rules1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.5: Sends request with a valid name and email for the user1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.6: Sends request with only lis_person_contact_email_primary but no name information1.0, 1.1, 1.1.1, 1.2ToDo
5.7: Sends valid user name information but no email address1.0, 1.1, 1.1.1, 1.2ToDo
5.8: Can suppress all identifiable user information1.0, 1.1, 1.1.1, 1.2ToDo
5.9: Send a lis_person_sourcedid1.0, 1.1, 1.1.1Pass
5.10: Send a role_scope_mentor1.1.1, 1.2ToDo
5.11: Send a lis_person_sourcedid1.2Pass
6: Context support 
6.1: Can send a context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
6.2: Can send a context_label1.0, 1.1, 1.1.1, 1.2Pass
6.3: Can send a context_title1.0, 1.1, 1.1.1, 1.2Pass
6.4: Can send a request without a context_id1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.5: Can send a context_type1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.6: Follows context_type rules1.0, 1.1, 1.1.1, 1.2, 2.0Pass
6.7: Send a lis_course_offering_sourcedid1.0, 1.1, 1.1.1, 1.2OK
6.8: Send a lis_course_section_sourcedid1.0, 1.1, 1.1.1OK
6.9: Send a lis_course_section_sourcedid1.2ToDo
7: Consumer support 
7.1: Can send a tool_consumer_instance_guid1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.2: Can send a tool_consumer_instance_name1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.3: Can send a tool_consumer_instance_description1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.4: Can send a tool_consumer_instance_contact_email1.0, 1.1, 1.1.1, 1.2, 2.0OK
8: Multiple Requests and Consistency 
8.1: Send message from a second resource_link_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.2: Sends a different user_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.3: Can send a different context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.4: Can send multiple resource_link_id values with the same context_id1.0, 1.1, 1.1.1, 1.2, 2.0OK
8.5: A resource_link_id never moves from one context_id to another1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.6: Consistency of context_id/user_id/role mappings1.0, 1.1, 1.1.1, 1.2, 2.0Pass
9: Launch Support 
9.1: Sends launch_presentation_locale parameter1.0, 1.1, 1.1.1, 1.2, 2.0Pass
9.2: launch_presentation_document_target parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.3: launch_presentation_width parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.4: launch_presentation_height parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.5: launch_presentation_css_url parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0Pass
9.6: launch_presentation_return_url parameter is valid1.2, 2.0Pass
10: Support for Outcomes Service 
10.1: Sends lis_result_sourcedid and lis_outcome_service_url parameter1.1, 1.1.1, OutcomesPass
10.2: Outcomes Service supports replaceResult operation1.1, 1.1.1, OutcomesPass
10.3: Outcomes Service supports readResult operation and returns the proper value1.1, 1.1.1, OutcomesPass
10.4: Outcomes Service supports deleteResult operation1.1, 1.1.1, OutcomesPass
10.5: Result is properly deleted after deleteResult operation1.1, 1.1.1, OutcomesPass
10.6: Outcomes Service properly handles unsupported operations1.1, 1.1.1, OutcomesPass
10.7: replaceResult does not accept out of range values1.1, 1.1.1, OutcomesPass
10.8: replaceResult accepts values of 0 and 11.1, 1.1.1, OutcomesPass
10.9: replaceResult does not accept invalid values1.1, 1.1.1, OutcomesPass
10.10: lis_outcome_service_url passed for all roles1.1, 1.1.1, OutcomesPass
10.11: Outcomes Service rejects invalid replaceResult requestOutcomesPass
10.12: Outcomes Service rejects invalid readResult requestOutcomesPass
10.13: Outcomes Service rejects invalid deleteResult requestOutcomesPass
11: Tool Consumer Profile 
11.1: URL does not change between launches1.2, 2.0Pass
11.2: Format matches media type1.2, 2.0Pass
11.3: Declares required capabilities1.2, 2.0Pass
11.4: Property values are consistent with launch parameters1.2, 2.0Pass
11.5: Required services are declared2.0Pass
12: Tool Settings 
12.1: Supports GET method2.0Pass
12.2: Supports PUT method2.0Pass
12.3: Supports PUT method using simple format2.0Pass
12.4: Supports bubble=all option2.0Pass
12.5: Supports bubble=distinct option2.0Pass
12.6: Rejects multi-level PUT requests2.0Pass
12.7: Rejects requests not properly signed2.0Pass


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Adam Marshall-2 Adam Marshall-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Are saying that the IMS LTI 2.0 spec is now finalised, published and is not subject to any more discussion / modification etc.?

 

I was talking to the folks from iParadigm yesterday who seemed to think it wouldn’t be published until mid 2015. I will correct them!

 

Good old Sakai – leading the field once more! Does this mean another tattoo then?

 

adam

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Severance
Sent: 14 February 2014 04:43
To: dev sakai
Subject: [Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

 

Hi all,

 

I just wanted to share that (a) IMS LTI 2.0 is final, and (b) Sakai-10 is the first officially certified LTI 2.0 Tool Consumer.

 

/Chuck

 

Begin forwarded message:



From: Charles Severance <[hidden email]>

Subject: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Date: February 12, 2014 at 3:02:28 PM EST

To: IMS LTI Certification submission <[hidden email]>

Cc: Charles Severance <[hidden email]>

 

Tests for: Sakai-10 (Alpha)

Ref: 9c4b2b44-fd14-442f-9962-6f1f71163848 for University of Michigan

I am submitting my results from the certification tests for your approval.

I have passed the certification tests for the following releases of LTI and wish to apply for certification:

1.     2.0

2.     Outcomes

Other comments:

Awesome technical support!

 

Confirmation statement

I confirm that the test results generated are an accurate representation of a properly executed certification testing process. I also confirm that I am familiar with the LTI specification and I am not aware of any circumstances when my application would fail the tests undertaken or fail to comply with any untested requirements of the specification.

Test results

Test

Required for

Status

1: Tool Registration

 

1.1: The contents of the registration request are valid

2.0

Pass

1.2: Invalid tool proxy is rejected

2.0

Pass

1.3: Valid tool proxy is accepted

2.0

Pass

2: Protocol Compliance and Resource Information

 

2.1: All launch messages have required parameters

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

2.2: Sends resource_link_title

1.0, 1.1, 1.1.1, 1.2

Pass

2.3: Sends resource_link_description

1.0, 1.1, 1.1.1, 1.2

OK

2.4: Sends tool_consumer_info_product_family_code

1.1, 1.1.1, 1.2

Pass

2.5: Sends tool_consumer_info_version

1.1, 1.1.1, 1.2

Pass

2.6: All messages have a recognised message type

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

3: OAuth and Signing Requests

 

3.1: Sign with agreed consumer key and secret

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

3.2: Can sign requests with URL parameters

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

3.3: Can sign a request with a URL parameter with space in the value parameter

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

3.4: Must include oauth_callback for OAuth 1.0A compliance

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

3.5: Parameters are encoded using UTF-8

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

4: Custom Field Support

 

4.1: Can send custom fields

1.0, 1.1, 1.1.1, 1.2

Pass

4.2: Properly maps special characters and case in custom fields

1.0, 1.1, 1.1.1, 1.2

ToDo

4.3: Supports $User.id substitution variable

1.2

Pass

4.4: Supports $User.username substitution variable

1.2

Pass

4.5: Supports $ToolConsumerProfile.url substitution variable

1.2, 2.0

Pass

4.6: Supports Tool Settings substitution variables

2.0

Pass

5: User Information

 

5.1: Sends a user_id

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

5.2: Sends Learner role

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

5.3: Sends Instructor role

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

5.4: Follows role naming rules

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

5.5: Sends request with a valid name and email for the user

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

5.6: Sends request with only lis_person_contact_email_primary but no name information

1.0, 1.1, 1.1.1, 1.2

ToDo

5.7: Sends valid user name information but no email address

1.0, 1.1, 1.1.1, 1.2

ToDo

5.8: Can suppress all identifiable user information

1.0, 1.1, 1.1.1, 1.2

ToDo

5.9: Send a lis_person_sourcedid

1.0, 1.1, 1.1.1

Pass

5.10: Send a role_scope_mentor

1.1.1, 1.2

ToDo

5.11: Send a lis_person_sourcedid

1.2

Pass

6: Context support

 

6.1: Can send a context_id

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

6.2: Can send a context_label

1.0, 1.1, 1.1.1, 1.2

Pass

6.3: Can send a context_title

1.0, 1.1, 1.1.1, 1.2

Pass

6.4: Can send a request without a context_id

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

6.5: Can send a context_type

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

6.6: Follows context_type rules

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

6.7: Send a lis_course_offering_sourcedid

1.0, 1.1, 1.1.1, 1.2

OK

6.8: Send a lis_course_section_sourcedid

1.0, 1.1, 1.1.1

OK

6.9: Send a lis_course_section_sourcedid

1.2

ToDo

7: Consumer support

 

7.1: Can send a tool_consumer_instance_guid

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

7.2: Can send a tool_consumer_instance_name

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

7.3: Can send a tool_consumer_instance_description

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

7.4: Can send a tool_consumer_instance_contact_email

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

8: Multiple Requests and Consistency

 

8.1: Send message from a second resource_link_id

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

8.2: Sends a different user_id

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

8.3: Can send a different context_id

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

8.4: Can send multiple resource_link_id values with the same context_id

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

8.5: A resource_link_id never moves from one context_id to another

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

8.6: Consistency of context_id/user_id/role mappings

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

9: Launch Support

 

9.1: Sends launch_presentation_locale parameter

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

9.2: launch_presentation_document_target parameter is valid

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

9.3: launch_presentation_width parameter is valid

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

9.4: launch_presentation_height parameter is valid

1.0, 1.1, 1.1.1, 1.2, 2.0

OK

9.5: launch_presentation_css_url parameter is valid

1.0, 1.1, 1.1.1, 1.2, 2.0

Pass

9.6: launch_presentation_return_url parameter is valid

1.2, 2.0

Pass

10: Support for Outcomes Service

 

10.1: Sends lis_result_sourcedid and lis_outcome_service_url parameter

1.1, 1.1.1, Outcomes

Pass

10.2: Outcomes Service supports replaceResult operation

1.1, 1.1.1, Outcomes

Pass

10.3: Outcomes Service supports readResult operation and returns the proper value

1.1, 1.1.1, Outcomes

Pass

10.4: Outcomes Service supports deleteResult operation

1.1, 1.1.1, Outcomes

Pass

10.5: Result is properly deleted after deleteResult operation

1.1, 1.1.1, Outcomes

Pass

10.6: Outcomes Service properly handles unsupported operations

1.1, 1.1.1, Outcomes

Pass

10.7: replaceResult does not accept out of range values

1.1, 1.1.1, Outcomes

Pass

10.8: replaceResult accepts values of 0 and 1

1.1, 1.1.1, Outcomes

Pass

10.9: replaceResult does not accept invalid values

1.1, 1.1.1, Outcomes

Pass

10.10: lis_outcome_service_url passed for all roles

1.1, 1.1.1, Outcomes

Pass

10.11: Outcomes Service rejects invalid replaceResult request

Outcomes

Pass

10.12: Outcomes Service rejects invalid readResult request

Outcomes

Pass

10.13: Outcomes Service rejects invalid deleteResult request

Outcomes

Pass

11: Tool Consumer Profile

 

11.1: URL does not change between launches

1.2, 2.0

Pass

11.2: Format matches media type

1.2, 2.0

Pass

11.3: Declares required capabilities

1.2, 2.0

Pass

11.4: Property values are consistent with launch parameters

1.2, 2.0

Pass

11.5: Required services are declared

2.0

Pass

12: Tool Settings

 

12.1: Supports GET method

2.0

Pass

12.2: Supports PUT method

2.0

Pass

12.3: Supports PUT method using simple format

2.0

Pass

12.4: Supports bubble=all option

2.0

Pass

12.5: Supports bubble=distinct option

2.0

Pass

12.6: Rejects multi-level PUT requests

2.0

Pass

12.7: Rejects requests not properly signed

2.0

Pass

 


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Adrian Fish-2 Adrian Fish-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

In reply to this post by Dr. Chuck
Superb. Nice work.


On 14 February 2014 04:43, Charles Severance <[hidden email]> wrote:
Hi all,

I just wanted to share that (a) IMS LTI 2.0 is final, and (b) Sakai-10 is the first officially certified LTI 2.0 Tool Consumer.

/Chuck

Begin forwarded message:

From: Charles Severance <[hidden email]>
Subject: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)
Date: February 12, 2014 at 3:02:28 PM EST
To: IMS LTI Certification submission <[hidden email]>
Cc: Charles Severance <[hidden email]>

Tests for: Sakai-10 (Alpha)

Ref: 9c4b2b44-fd14-442f-9962-6f1f71163848 for University of Michigan

I am submitting my results from the certification tests for your approval.

I have passed the certification tests for the following releases of LTI and wish to apply for certification:

  1. 2.0
  2. Outcomes

Other comments:

Awesome technical support!

Confirmation statement

I confirm that the test results generated are an accurate representation of a properly executed certification testing process. I also confirm that I am familiar with the LTI specification and I am not aware of any circumstances when my application would fail the tests undertaken or fail to comply with any untested requirements of the specification.

Test results

TestRequired forStatus
1: Tool Registration  
1.1: The contents of the registration request are valid2.0Pass
1.2: Invalid tool proxy is rejected 2.0Pass
1.3: Valid tool proxy is accepted2.0 Pass
2: Protocol Compliance and Resource Information 
2.1: All launch messages have required parameters1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
2.2: Sends resource_link_title1.0, 1.1, 1.1.1, 1.2Pass
2.3: Sends resource_link_description 1.0, 1.1, 1.1.1, 1.2OK
2.4: Sends tool_consumer_info_product_family_code1.1, 1.1.1, 1.2 Pass
2.5: Sends tool_consumer_info_version1.1, 1.1.1, 1.2Pass
2.6: All messages have a recognised message type 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3: OAuth and Signing Requests 
3.1: Sign with agreed consumer key and secret1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.2: Can sign requests with URL parameters 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.3: Can sign a request with a URL parameter with space in the value parameter 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.4: Must include oauth_callback for OAuth 1.0A compliance1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
3.5: Parameters are encoded using UTF-81.0, 1.1, 1.1.1, 1.2, 2.0 Pass
4: Custom Field Support 
4.1: Can send custom fields1.0, 1.1, 1.1.1, 1.2 Pass
4.2: Properly maps special characters and case in custom fields1.0, 1.1, 1.1.1, 1.2ToDo
4.3: Supports $User.id substitution variable 1.2Pass
4.4: Supports $User.username substitution variable1.2 Pass
4.5: Supports $ToolConsumerProfile.url substitution variable1.2, 2.0Pass
4.6: Supports Tool Settings substitution variables 2.0Pass
5: User Information 
5.1: Sends a user_id 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.2: Sends Learner role1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
5.3: Sends Instructor role1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.4: Follows role naming rules 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.5: Sends request with a valid name and email for the user1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
5.6: Sends request with only lis_person_contact_email_primary but no name information1.0, 1.1, 1.1.1, 1.2 ToDo
5.7: Sends valid user name information but no email address1.0, 1.1, 1.1.1, 1.2 ToDo
5.8: Can suppress all identifiable user information1.0, 1.1, 1.1.1, 1.2ToDo
5.9: Send a lis_person_sourcedid 1.0, 1.1, 1.1.1Pass
5.10: Send a role_scope_mentor1.1.1, 1.2 ToDo
5.11: Send a lis_person_sourcedid1.2Pass
6: Context support  
6.1: Can send a context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
6.2: Can send a context_label 1.0, 1.1, 1.1.1, 1.2Pass
6.3: Can send a context_title1.0, 1.1, 1.1.1, 1.2 Pass
6.4: Can send a request without a context_id1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.5: Can send a context_type 1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.6: Follows context_type rules1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
6.7: Send a lis_course_offering_sourcedid1.0, 1.1, 1.1.1, 1.2OK
6.8: Send a lis_course_section_sourcedid 1.0, 1.1, 1.1.1OK
6.9: Send a lis_course_section_sourcedid1.2 ToDo
7: Consumer support 
7.1: Can send a tool_consumer_instance_guid1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
7.2: Can send a tool_consumer_instance_name1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.3: Can send a tool_consumer_instance_description 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.4: Can send a tool_consumer_instance_contact_email1.0, 1.1, 1.1.1, 1.2, 2.0 OK
8: Multiple Requests and Consistency 
8.1: Send message from a second resource_link_id 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.2: Sends a different user_id1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
8.3: Can send a different context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.4: Can send multiple resource_link_id values with the same context_id 1.0, 1.1, 1.1.1, 1.2, 2.0OK
8.5: A resource_link_id never moves from one context_id to another1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
8.6: Consistency of context_id/user_id/role mappings1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9: Launch Support 
9.1: Sends launch_presentation_locale parameter1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9.2: launch_presentation_document_target parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.3: launch_presentation_width parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.4: launch_presentation_height parameter is valid 1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.5: launch_presentation_css_url parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9.6: launch_presentation_return_url parameter is valid1.2, 2.0 Pass
10: Support for Outcomes Service 
10.1: Sends lis_result_sourcedid and lis_outcome_service_url parameter1.1, 1.1.1, Outcomes Pass
10.2: Outcomes Service supports replaceResult operation1.1, 1.1.1, OutcomesPass
10.3: Outcomes Service supports readResult operation and returns the proper value 1.1, 1.1.1, OutcomesPass
10.4: Outcomes Service supports deleteResult operation1.1, 1.1.1, Outcomes Pass
10.5: Result is properly deleted after deleteResult operation1.1, 1.1.1, Outcomes Pass
10.6: Outcomes Service properly handles unsupported operations1.1, 1.1.1, OutcomesPass
10.7: replaceResult does not accept out of range values1.1, 1.1.1, OutcomesPass
10.8: replaceResult accepts values of 0 and 1 1.1, 1.1.1, OutcomesPass
10.9: replaceResult does not accept invalid values1.1, 1.1.1, Outcomes Pass
10.10: lis_outcome_service_url passed for all roles1.1, 1.1.1, OutcomesPass
10.11: Outcomes Service rejects invalid replaceResult request OutcomesPass
10.12: Outcomes Service rejects invalid readResult requestOutcomes Pass
10.13: Outcomes Service rejects invalid deleteResult requestOutcomesPass
11: Tool Consumer Profile  
11.1: URL does not change between launches1.2, 2.0Pass
11.2: Format matches media type 1.2, 2.0Pass
11.3: Declares required capabilities1.2, 2.0 Pass
11.4: Property values are consistent with launch parameters1.2, 2.0Pass
11.5: Required services are declared 2.0Pass
12: Tool Settings 
12.1: Supports GET method 2.0Pass
12.2: Supports PUT method2.0 Pass
12.3: Supports PUT method using simple format2.0Pass
12.4: Supports bubble=all option 2.0Pass
12.5: Supports bubble=distinct option2.0 Pass
12.6: Rejects multi-level PUT requests2.0Pass
12.7: Rejects requests not properly signed 2.0Pass


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Steve Swinsburg-3 Steve Swinsburg-3
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Awesome.


On Sat, Feb 15, 2014 at 2:27 AM, Adrian Fish <[hidden email]> wrote:
Superb. Nice work.


On 14 February 2014 04:43, Charles Severance <[hidden email]> wrote:
Hi all,

I just wanted to share that (a) IMS LTI 2.0 is final, and (b) Sakai-10 is the first officially certified LTI 2.0 Tool Consumer.

/Chuck

Begin forwarded message:

From: Charles Severance <[hidden email]>
Subject: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)
Date: February 12, 2014 at 3:02:28 PM EST
To: IMS LTI Certification submission <[hidden email]>
Cc: Charles Severance <[hidden email]>

Tests for: Sakai-10 (Alpha)

Ref: 9c4b2b44-fd14-442f-9962-6f1f71163848 for University of Michigan

I am submitting my results from the certification tests for your approval.

I have passed the certification tests for the following releases of LTI and wish to apply for certification:

  1. 2.0
  2. Outcomes

Other comments:

Awesome technical support!

Confirmation statement

I confirm that the test results generated are an accurate representation of a properly executed certification testing process. I also confirm that I am familiar with the LTI specification and I am not aware of any circumstances when my application would fail the tests undertaken or fail to comply with any untested requirements of the specification.

Test results

TestRequired forStatus
1: Tool Registration  
1.1: The contents of the registration request are valid2.0Pass
1.2: Invalid tool proxy is rejected 2.0Pass
1.3: Valid tool proxy is accepted2.0 Pass
2: Protocol Compliance and Resource Information 
2.1: All launch messages have required parameters1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
2.2: Sends resource_link_title1.0, 1.1, 1.1.1, 1.2Pass
2.3: Sends resource_link_description 1.0, 1.1, 1.1.1, 1.2OK
2.4: Sends tool_consumer_info_product_family_code1.1, 1.1.1, 1.2 Pass
2.5: Sends tool_consumer_info_version1.1, 1.1.1, 1.2Pass
2.6: All messages have a recognised message type 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3: OAuth and Signing Requests 
3.1: Sign with agreed consumer key and secret1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.2: Can sign requests with URL parameters 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.3: Can sign a request with a URL parameter with space in the value parameter 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
3.4: Must include oauth_callback for OAuth 1.0A compliance1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
3.5: Parameters are encoded using UTF-81.0, 1.1, 1.1.1, 1.2, 2.0 Pass
4: Custom Field Support 
4.1: Can send custom fields1.0, 1.1, 1.1.1, 1.2 Pass
4.2: Properly maps special characters and case in custom fields1.0, 1.1, 1.1.1, 1.2ToDo
4.3: Supports $User.id substitution variable 1.2Pass
4.4: Supports $User.username substitution variable1.2 Pass
4.5: Supports $ToolConsumerProfile.url substitution variable1.2, 2.0Pass
4.6: Supports Tool Settings substitution variables 2.0Pass
5: User Information 
5.1: Sends a user_id 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.2: Sends Learner role1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
5.3: Sends Instructor role1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.4: Follows role naming rules 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
5.5: Sends request with a valid name and email for the user1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
5.6: Sends request with only lis_person_contact_email_primary but no name information1.0, 1.1, 1.1.1, 1.2 ToDo
5.7: Sends valid user name information but no email address1.0, 1.1, 1.1.1, 1.2 ToDo
5.8: Can suppress all identifiable user information1.0, 1.1, 1.1.1, 1.2ToDo
5.9: Send a lis_person_sourcedid 1.0, 1.1, 1.1.1Pass
5.10: Send a role_scope_mentor1.1.1, 1.2 ToDo
5.11: Send a lis_person_sourcedid1.2Pass
6: Context support  
6.1: Can send a context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
6.2: Can send a context_label 1.0, 1.1, 1.1.1, 1.2Pass
6.3: Can send a context_title1.0, 1.1, 1.1.1, 1.2 Pass
6.4: Can send a request without a context_id1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.5: Can send a context_type 1.0, 1.1, 1.1.1, 1.2, 2.0OK
6.6: Follows context_type rules1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
6.7: Send a lis_course_offering_sourcedid1.0, 1.1, 1.1.1, 1.2OK
6.8: Send a lis_course_section_sourcedid 1.0, 1.1, 1.1.1OK
6.9: Send a lis_course_section_sourcedid1.2 ToDo
7: Consumer support 
7.1: Can send a tool_consumer_instance_guid1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
7.2: Can send a tool_consumer_instance_name1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.3: Can send a tool_consumer_instance_description 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
7.4: Can send a tool_consumer_instance_contact_email1.0, 1.1, 1.1.1, 1.2, 2.0 OK
8: Multiple Requests and Consistency 
8.1: Send message from a second resource_link_id 1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.2: Sends a different user_id1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
8.3: Can send a different context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass
8.4: Can send multiple resource_link_id values with the same context_id 1.0, 1.1, 1.1.1, 1.2, 2.0OK
8.5: A resource_link_id never moves from one context_id to another1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
8.6: Consistency of context_id/user_id/role mappings1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9: Launch Support 
9.1: Sends launch_presentation_locale parameter1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9.2: launch_presentation_document_target parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.3: launch_presentation_width parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.4: launch_presentation_height parameter is valid 1.0, 1.1, 1.1.1, 1.2, 2.0OK
9.5: launch_presentation_css_url parameter is valid1.0, 1.1, 1.1.1, 1.2, 2.0 Pass
9.6: launch_presentation_return_url parameter is valid1.2, 2.0 Pass
10: Support for Outcomes Service 
10.1: Sends lis_result_sourcedid and lis_outcome_service_url parameter1.1, 1.1.1, Outcomes Pass
10.2: Outcomes Service supports replaceResult operation1.1, 1.1.1, OutcomesPass
10.3: Outcomes Service supports readResult operation and returns the proper value 1.1, 1.1.1, OutcomesPass
10.4: Outcomes Service supports deleteResult operation1.1, 1.1.1, Outcomes Pass
10.5: Result is properly deleted after deleteResult operation1.1, 1.1.1, Outcomes Pass
10.6: Outcomes Service properly handles unsupported operations1.1, 1.1.1, OutcomesPass
10.7: replaceResult does not accept out of range values1.1, 1.1.1, OutcomesPass
10.8: replaceResult accepts values of 0 and 1 1.1, 1.1.1, OutcomesPass
10.9: replaceResult does not accept invalid values1.1, 1.1.1, Outcomes Pass
10.10: lis_outcome_service_url passed for all roles1.1, 1.1.1, OutcomesPass
10.11: Outcomes Service rejects invalid replaceResult request OutcomesPass
10.12: Outcomes Service rejects invalid readResult requestOutcomes Pass
10.13: Outcomes Service rejects invalid deleteResult requestOutcomesPass
11: Tool Consumer Profile  
11.1: URL does not change between launches1.2, 2.0Pass
11.2: Format matches media type 1.2, 2.0Pass
11.3: Declares required capabilities1.2, 2.0 Pass
11.4: Property values are consistent with launch parameters1.2, 2.0Pass
11.5: Required services are declared 2.0Pass
12: Tool Settings 
12.1: Supports GET method 2.0Pass
12.2: Supports PUT method2.0 Pass
12.3: Supports PUT method using simple format2.0Pass
12.4: Supports bubble=all option 2.0Pass
12.5: Supports bubble=distinct option2.0 Pass
12.6: Rejects multi-level PUT requests2.0Pass
12.7: Rejects requests not properly signed 2.0Pass


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Dr. Chuck Dr. Chuck
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

In reply to this post by Adam Marshall-2

On Feb 14, 2014, at 5:22 AM, Adam Marshall <[hidden email]> wrote:

Are saying that the IMS LTI 2.0 spec is now finalised, published and is not subject to any more discussion / modification etc.?
 
I was talking to the folks from iParadigm yesterday who seemed to think it wouldn’t be published until mid 2015. I will correct them!
 
Good old Sakai – leading the field once more! Does this mean another tattoo then?
 
adam

Yes - The Spec has been finalised and published for over a month.   

What got finished this week was the certification test.  In effect IMS insists that the certification test is not official until at least two real products can pass the certification test.   The two products that were used to certify the certification were Sakai and Vitalsource.  It is a bit of a rough go for the first two (pioneers with arrows in their back and all) that pass the test because as we progress through months of iterations sometimes the spec is changed, sometimes the implementations are changed, and sometimes the tests change and all the way we make sure that we maintain consensus by meeting and approving each tweak.  We have had a working-but-not-final LTI 2.0 implementation in Sakai since the summer - but if you look a the commits you will see that it has evolved as last minute changes were made to the spec and tests as we found and fixed little mistakes or rough edges here and there.  Thankfully, I have good financial support for all the travel and my time spent coding because writing LTI 2.0 and participating in the finalisation of the spec has nearly been a year of heavy effort.

So it is open season on LTI 2.0.   Folks can start developing now, Sakai's nightly server functions as the best test harness for LTI 2.0 that is available :)  There is code for Java, PHP, and Rails in various stages of maturity.   The reusable Java and PHP code I wrote is of course Apache-licensed -  some of the other code is not yet publicly available.

In terms of Tattoos, I will likely do something when the first mainstream LMS ships LTI 2.0...  Which I hope to see before the end of this year.

/Chuck



_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Steve Swinsburg-3 Steve Swinsburg-3
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Whats the LTI2 logo and we can all get them ;)


On Sun, Feb 16, 2014 at 12:19 AM, Charles Severance <[hidden email]> wrote:

On Feb 14, 2014, at 5:22 AM, Adam Marshall <[hidden email]> wrote:

Are saying that the IMS LTI 2.0 spec is now finalised, published and is not subject to any more discussion / modification etc.?
 
I was talking to the folks from iParadigm yesterday who seemed to think it wouldn’t be published until mid 2015. I will correct them!
 
Good old Sakai – leading the field once more! Does this mean another tattoo then?
 
adam

Yes - The Spec has been finalised and published for over a month.   

What got finished this week was the certification test.  In effect IMS insists that the certification test is not official until at least two real products can pass the certification test.   The two products that were used to certify the certification were Sakai and Vitalsource.  It is a bit of a rough go for the first two (pioneers with arrows in their back and all) that pass the test because as we progress through months of iterations sometimes the spec is changed, sometimes the implementations are changed, and sometimes the tests change and all the way we make sure that we maintain consensus by meeting and approving each tweak.  We have had a working-but-not-final LTI 2.0 implementation in Sakai since the summer - but if you look a the commits you will see that it has evolved as last minute changes were made to the spec and tests as we found and fixed little mistakes or rough edges here and there.  Thankfully, I have good financial support for all the travel and my time spent coding because writing LTI 2.0 and participating in the finalisation of the spec has nearly been a year of heavy effort.

So it is open season on LTI 2.0.   Folks can start developing now, Sakai's nightly server functions as the best test harness for LTI 2.0 that is available :)  There is code for Java, PHP, and Rails in various stages of maturity.   The reusable Java and PHP code I wrote is of course Apache-licensed -  some of the other code is not yet publicly available.

In terms of Tattoos, I will likely do something when the first mainstream LMS ships LTI 2.0...  Which I hope to see before the end of this year.

/Chuck



_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Alex Ballesté-2 Alex Ballesté-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

Thanks Chuck for the effort you've done in this area. It's a great contribution.

Alex.

On 17 de febrer de 2014 0.01.43 CET, Steve Swinsburg <[hidden email]> wrote:
Whats the LTI2 logo and we can all get them ;)


On Sun, Feb 16, 2014 at 12:19 AM, Charles Severance <[hidden email]> wrote:

On Feb 14, 2014, at 5:22 AM, Adam Marshall <[hidden email]> wrote:

Are saying that the IMS LTI 2.0 spec is now finalised, published and is not subject to any more discussion / modification etc.?
 
I was talking to the folks from iParadigm yesterday who seemed to think it wouldn’t be published until mid 2015. I will correct them!
 
Good old Sakai – leading the field once more! Does this mean another tattoo then?
 
adam

Yes - The Spec has been finalised and published for over a month.   

What got finished this week was the certification test.  In effect IMS insists that the certification test is not official until at least two real products can pass the certification test.   The two products that were used to certify the certification were Sakai and Vitalsource.  It is a bit of a rough go for the first two (pioneers with arrows in their back and all) that pass the test because as we progress through months of iterations sometimes the spec is changed, sometimes the implementations are changed, and sometimes the tests change and all the way we make sure that we maintain consensus by meeting and approving each tweak.  We have had a working-but-not-final LTI 2.0 implementation in Sakai since the summer - but if you look a the commits you will see that it has evolved as last minute changes were made to the spec and tests as we found and fix ed little mistakes or rough edges here and there.  Thankfully, I have good financial support for all the travel and my time spent coding because writing LTI 2.0 and participating in the finalisation of the spec has nearly been a year of heavy effort.

So it is open season on LTI 2.0.   Folks can start developing now, Sakai's nightly server functions as the best test harness for LTI 2.0 that is available :)  There is code for Java, PHP, and Rails in various stages of maturity.   The reusable Java and PHP code I wrote is of course Apache-licensed -  some of the other code is not yet publicly available.

In terms of Tattoos, I will likely do something when the first mainstream LMS ships LTI 2.0...  Which I hope to see before the end of this year.

/Chuck



_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"



sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"

--
Sent from my Galaxy Note II. Please excuse my brevity.
_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Dr. Chuck Dr. Chuck
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Building Sakai] LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

In reply to this post by Steve Swinsburg-3
Here is the logo - I should put it in the code base.

/Chuck

On Feb 16, 2014, at 6:01 PM, Steve Swinsburg <[hidden email]> wrote:

Whats the LTI2 logo and we can all get them ;)


On Sun, Feb 16, 2014 at 12:19 AM, Charles Severance <[hidden email]> wrote:

On Feb 14, 2014, at 5:22 AM, Adam Marshall <[hidden email]> wrote:

Are saying that the IMS LTI 2.0 spec is now finalised, published and is not subject to any more discussion / modification etc.?
 
I was talking to the folks from iParadigm yesterday who seemed to think it wouldn’t be published until mid 2015. I will correct them!
 
Good old Sakai – leading the field once more! Does this mean another tattoo then?
 
adam

Yes - The Spec has been finalised and published for over a month.   

What got finished this week was the certification test.  In effect IMS insists that the certification test is not official until at least two real products can pass the certification test.   The two products that were used to certify the certification were Sakai and Vitalsource.  It is a bit of a rough go for the first two (pioneers with arrows in their back and all) that pass the test because as we progress through months of iterations sometimes the spec is changed, sometimes the implementations are changed, and sometimes the tests change and all the way we make sure that we maintain consensus by meeting and approving each tweak.  We have had a working-but-not-final LTI 2.0 implementation in Sakai since the summer - but if you look a the commits you will see that it has evolved as last minute changes were made to the spec and tests as we found and fixed little mistakes or rough edges here and there.  Thankfully, I have good financial support for all the travel and my time spent coding because writing LTI 2.0 and participating in the finalisation of the spec has nearly been a year of heavy effort.

So it is open season on LTI 2.0.   Folks can start developing now, Sakai's nightly server functions as the best test harness for LTI 2.0 that is available :)  There is code for Java, PHP, and Rails in various stages of maturity.   The reusable Java and PHP code I wrote is of course Apache-licensed -  some of the other code is not yet publicly available.

In terms of Tattoos, I will likely do something when the first mainstream LMS ships LTI 2.0...  Which I hope to see before the end of this year.

/Chuck



_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"



_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Loading...