Hi Matthias,
Thanks once again for your quick reply.
>In terms of run-time environments, there's a quite a difference between
>IMS and SCORM. First, IMS doesn't provide one 😊
Runtime in the more narrow sense - ok. But one may think of is just
a DELIVERY entity that acts "at run time"
Yes, after reading yout comments on IMS SS, I think you are absolutely right.
I think I was understanding delivery as "delivery environment".
But you are absolutely right in the sense that IMS SS does specify sequences and conditions for this sequences to ocurr within a delivery environment.
I still don't get rid of the impression that Scorm DOES have a slightly
different focus (more client - server division of labor than just on the
browser-to-webserver basis, more sophisticated production tools
necessary),
Yes, that's correct. In addition, you might want to take into account why SCORM wants to have such environment for delivering content and it has to do (I believe) with the fact that want to make sure their content runs in "every SCORM runtime environment" regardless whether the medium (a cellphone, or any type of browser as long as it has an applet that acts as underlying communicator between the browser functions (usually on javascript) and the back end server.
so I don't think we can say, IMS leaves the delivery
up to the competitor standard.
Yes, that is true. However, it is kind of difficult to me to put them both at the same level. SCORM uses IMS SS now (in version 1.3), so it is entirely based on IMS SS for the conditions of delivery of content.
However as you quoted before, IMS doesn't specify the underlying delivery mechanisms (which SCORM took from AICC)
Thanks,
Ernie
