6 Replies
Vincent Scoma

Hi Camille,

Great question! 

Tin Can API doesn't have the same type of data limits as a SCORM 1.2 package would. To avoid reaching that data limit that can be imposed by some LMSs, we do recommend publishing with the latest edition of SCORM 2004 or Tin Can API. For more details on the resume behavior for Tin Can API, this guide should help point you in the right direction: 

Please let us know if you have any questions! 

Jimmi Thøgersen

Just to expand a bit on Vincent's answer... The specification for Tin Can specifically allows any limit - it leaves it up to the LRS to decide (with the restriction that the limit can at least be configured to be high enough to allow the sizes the LRS conformance tests need):

"The LRS MAY choose any Attachment, Statement and document size limits and MAY vary this limit on any basis, e.g., per authority." (my emphasis)

The way Storyline saves suspend-data to TinCan is in a "document".

That said, it's highly unlikely that an LRS will enforce limits on documents as low as SCORM 1.2's limit on suspend-data (4096 characters) - or even SCORM 2004's (64000 characters).

But it's still worth being aware that it may, and that it's allowed to even vary that limit based on anything it likes. I.e. different courses may get different limits,different learners may get different limits - it might even base the limit on time of day ;-) It's all up to the individual LRS.

Jimmi Thøgersen
JC Caianiello

What does  LRS stand for?

Learning Record Store - it's the part of TinCan/xAPI where completion, score, progress etc. is stored - in some ways it's similar to an LMS, and it may be part of an LMS, but doesn't need to - the LRS is only intended for storing and retrieving tracking data. Unlike the LMS in SCORM, the LRS doesn't need to actually launch/display the course - the course just needs to know where to send the data (where the LRS is located), which doesn't need to be where the course is located.