Hi Ola,
In fact, SCORM essentially just adds a strictly specified front-end
to IMS Simple Sequencing, which mandates a javascript client called
"runtime environment".
Yes. However, that is partially true.
SCORM uses an API adapter on the client side not just for IMS SS
purposes but also to manage most of its interaction between the user and
the course content. For instance, on startup the content looks for the
API adapter (which it could be a javascript, an applet, activeX, flash,
or whatever) to initialize the course delivery. Then the content "talks"
to the LMS only thru the API.
While it is correct to say that the API tracks the student progress and
delivers the content following the course sequencing, it also passes
score results, information about the user, etc back and forward from the
LMS and the user.
2) There is no reason to build this spec into the LORS package, since
simple sequencing isn't necessarily dependent on learning objects
being stored in this or that package - the simple sequencing package
has to be integrated with Assessment, too, for example.
Yeah, that is right. That's why LORS is a library of IMS specifications
(so far IMS CP and MD) available for all packages to be used.
Back in May 2003, I suggested you to do the implement IMS SS as a
library so other applications could make use of it, and this was your
answer:
Ernie: To answer your questions - no, I don't believe there will be a
public API to the simple sequencing engine. Since there is no
obvious client to the SS engine besides the Curriculum package, I
think it's quite clear that SS could as well reside within the
Curriculum package borders.
https://openacs.org/forums/message-view?message_id=102631
So, I'm happy you have changed your mind 😊
Do you think we can have an API for IMS SS soon?
Ernie
