I am developing an API to handle SCORM 2004, I want to implement sequencing and navigation algorithm.
In the SCORM 2004 manual, he wrote: "The termination process receives an end-to-date request from the navigation process, and terminates the current activity." Based on the type of expiration request "
Be sure to end the request? How can I read the value of "termination request" in the termination function?
Expiry requests are not necessarily in continuation, consider them as a parameter in the termination request process. Has passed. The termination request process is passed to which the expiration request is determined by the return value of the navigation request process (you can not read it from the termination function).
You can find a list of possible termination requests values in Section 4.5.1 of the Sequencing and Navigation Book (I am referring to the SCORM 2004 4th edition, this page on SN-4-27 .)
You may also want to see this picture indexed pseudocode algorithms are related to each other.
This "sequencing loop" is executed in response to a navigation request. A navigation request can be triggered in one of two ways, either, the SCO sets an adl.nav.request value via run-time or the user clicks on an LMS user interface element.
In the case of SCO, a request will be made once the SCO call is completed, after the indexing process, SCO, which is specified in the SCO, will be given in the indexing process. .
In the case of a user who initiated an NAV request through LMS, LMS will first unload the SCO (due to call SCO termination) and after that it will implement the entire sequencing process. And it will pass on the user navigation navigation request.
Comments
Post a Comment