|
SCORM™ 2004
Known Issues
Stay Ahead of the Class With Great Tips To Get Prepared For College!
- Issue 11374: Content Packages containing a <ruleCondtion> element that reference objectives within a lt;sequencingCollection> element may fail Course Import
SCORM Content Packages that include sequencing information where <sequencingRules> reference <objectives> contained in a <seqeuncingCollection> fail to successfully import. In these cases, the Sample Run-Time Environment (RTE) does not correctly recognize the objective IDs contained in the <sequencingCollection> and incorrectly flags the Content Package as non-conformant; failing the import process.
- Issue 11373: Content Packages containing a <ruleCondtion> element that reference objectives within a <sequencingCollection> element may fail validation
SCORM Content Packages that include sequencing information where reference <objectives> contained in a <seqeuncingCollection> fail to pass conformance. In these cases, the Conformance Test Suite Content Package Test does not correctly recognize the objective IDs contained in the <sequencingCollection> and produces an "Objective ID is not local to the Activity" error.
- Issue 11301: LMS DMI Test Content Package may throw ArrayIndexOutOfBounds Exception
A Java "Array Index Out Of Bounds" Exception may occur in the LMS Conformance Test when running the LMS DMI Test Content Package. This exception can occur if an LMS returns an unexpected (invalid) value for some GetValue() calls. The LMS Conformance Test was not configured to accept all unexpected responses from GetValue() calls.
- Issue 11298: Summary Log File cannot be opened after Abort Button Clicked in Content Package Conformance Test
In the Content Package Conformance Test, when a SCO is being tested, if the user presses the “Abort” button within the Conformance Test Suite interface or if the test is abnormally terminated, the Content Package Test Summary Log is not properly closed. This prevents the Summary Log from rendering correctly; opening the file will result in a well-formness error being displayed.. In this situation, the Detailed Log file will continue to render properly.
- Issue 11293: The Sample Run-Time Environment does not correctly handle resource href URIs containing the ‘../’ expression.
The Sample Run-Time Environment does not properly handle the existence of the “../”syntax properly when it occurs within href URI values within an imsmanifest.xml. During validation, href values containing a ‘../’ expression will either generate the Best Practice Warning produced when files in the content package are not referenced in the manifest, or an error message indicating the resource whose path contains the ‘../’ could not be found in the package. This issue was partially resolved in the SCORM 2004 3rd Edition Sample Run-Time Environment Version 1.0.1. However, the issue still exists for href values which contain the ‘../’ syntax and are referenced through a resource dependency element.
- Issue 11292: The Conformance Test Suite Content Package Test does not correctly handle resource href URIs containing the ‘../’ expression.
The Conformance Test Suite Content Package Conformance Test does not always handle the existence of the “../” syntax properly when it occurs within href URI values within an imsmanifest.xml. During validation, href values containing a ‘../’ expression will either generate a Best Practice Warning produced when files in the content package are not referenced in the manifest, or an error message indicating the resource whose path containing the ‘../’ expression could not be found in the package. This issue was partially resolved in the SCORM 2004 3rd Edition Conformance Test Suite Version 1.0.1. However, the issue still exists for href values which contain the ‘../’ syntax and are referenced through a resource dependency element.
- Issue 11291: Line return characters in imsmanifest.xml and Data Model elements may produce JavaScript errors
When API Data Model Logging is active, the Sample RTE will throw a JavaScript error when attempting to log, from a GetValue() call, data model values that include new line and carriage return characters. One source of this error is the imsmanifest.xml element <adlcp:dataFromLMS>. If this element contains any new line or carriage return characters (‘\n’ or ‘\r’), a JavaScript error will be thrown if a GetValue() call is made on the “cmi.launch_data” data model element while API Data Model Logging is active.
- Issue 11225: DMTimeUtility throws ArrayIndexOutOfBounds Exception
An ArrayIndexOutOfBounds Exception may occur in the Sample Run-Time Environment (RTE) when a SCO attempts to set the value for a data model element of type “timeinterval” (e.g. cmi.session_time). This exception can occur when the value being set does not include some number of hours. For example, a user will encounter an ArrayIndexOutOfBounds Exception if a SCO tries to set the cmi.session_time data model element to the value of “P1DT1M0.55S”.
- Issue 11296: Receiving a 1609 Error during Sample Run-Time Environment Install
In some cases, during installation of the SCORM 2004 3rd Edition Sample Run-Time
Environment Version 1.0.1 (from installer download dated April 5, 2007), an
error message may be encountered.
- Issue 10899: Incorrect Description of the <deliveryControls> Element
The SCORM 2004 3rd Edition Content Aggregation Model contains an incorrect narrative description of the Element.
- Issue 11023: Contradictory Requirement for Processing an adl.nav.request
The SCORM 2004 3rd Edition Sequencing and Navigation document contains language that is not accurate with the processing of an adl.nav.request data model element. The document does not consistently describe this processing behavior.
- Issue 11188: Sample Run-Time Environment doesn't check for illegal reserved characters in URI values during validation.
The Sample Run-Time Environment (RTE) does not check for illegal reserved characters in URI values in an imsmanifest.xml file during validation. As a result, packages with manifests containing non-encoded accented characters or blank spaces incorrectly pass validation The Sample RTE will be modified to correctly check for non-encoded reserved characters in URI values of a manifest and display an appropriate error message when they exist.
- Issue 10815: The Sample Run-Time Environment incorrectly processing cmi.exit equal to "logout"
The SCORM 2004 3rd Edition Sample Run-Time Environment (RTE) does not recognize when a SCO sets cmi.exit equal to logout and then ends its attempt. Instead of ending the current attempt on the Activity Tree by processing an Exit All Navigation Request, as defined in the SCORM 2004 3rd Edition Conformance Requirements, the Sample RTE processes any pending Navigation Request invoked by the learner via the LMS User Interface or indicated by the SCO via the SCORM Navigation Data Model.
- Issue 10899: Incorrect Description of the <deliveryControls> Element
The SCORM 2004 3rd Edition Content Aggregation Model contains an incorrect narrative description of the Element.
- Issue 11023: Contradictory Requirement for Processing an adl.nav.request
The SCORM 2004 3rd Edition Sequencing and Navigation document contains language that is not accurate with the processing of an adl.nav.request data model element. The document does not consistently describe this processing behavior.
- Issue 11188: Sample Run-Time Environment doesn't check for illegal reserved characters in URI values during validation.
The Sample Run-Time Environment (RTE) does not check for illegal reserved characters in URI values in an imsmanifest.xml file during validation. As a result, packages with manifests containing non-encoded accented characters or blank spaces incorrectly pass validation The Sample RTE will be modified to correctly check for non-encoded reserved characters in URI values of a manifest and display an appropriate error message when they exist.
- Issue 10815: The Sample Run-Time Environment incorrectly processing cmi.exit equal to "logout"
The SCORM 2004 3rd Edition Sample Run-Time Environment (RTE) does not recognize when a SCO sets cmi.exit equal to logout and then ends its attempt. Instead of ending the current attempt on the Activity Tree by processing an Exit All Navigation Request, as defined in the SCORM 2004 3rd Edition Conformance Requirements, the Sample RTE processes any pending Navigation Request invoked by the learner via the LMS User Interface or indicated by the SCO via the SCORM Navigation Data Model.
- Issue 10783: Internal Walk-off-the-Tree Behavior
The SCORM 2004 3rd Edition Sample Run-Time Environment (RTE) does not correctly process Continue Sequencing Requests that would cause the Sequencing Request tree traversal to walk-off-the-tree. In cases where processing a Continue Sequencing Request fails to identify an activity for deliver due to encountering a Sequencing Control Mode Flow equal False cluster or a disabled activity, the Sample RTE displays the BLOCKED interstitial page instead of processing an Exit All Navigation Request as defined in the sequencing pseudo-code (SCORM SN Book, Appendix C).
- Issue 10538: Incorrect Response Expected from User Interface Interoperability Question in LMS Test Content Package CM-07d
In LMS Test Content Package CM-07d, from Activity 6 (step 3), the SCORM 2004 3rd Edition Conformance Test Suite Version 1.0 is expecting the root of the Activity Tree to be an unavailable target of Choice. In this case, the root of the Activity Tree is the common ancestor of the Current Activity and itself (the target of the Choice Navigation Request). The "constrained choice" attribute on Activity 4 should not prevent the Root from being selectable because the "constrained choice" attribute is not considered when targeting a common ancestor (Choice Sequencing Request Process SB.2.9, case 4).
- Issue 9956: Director SCO of the PITE Example Never Terminates
Upon viewing the html page when exiting, the poster noticed that there IS NO 'unLoadPage' browser function.
- Issue 9955: Unreferenced Files in All Five imsmanifest.xml Files
There are unreferenced files in all five course manifests.
- Issue 9273: Duplicate Files in the Zipped Content Package
There are multiple duplicate files in the zipped content package.
- Issue 8880: Completion Status Application Error
In the application module of Completion Threshold, the example sets cmi.completion_status to "complete".
- Issue 7980: Inconsistency in imsmanifest.xml for the DMCE Version 1.0
In the Data Model Content Examples (DMCE) Version 1.0, the manifest contains some extraneous files and in other cases, missing files.
- Issue 8592: Incorrect ID in Figure 3.4.2.1b
|
|
