![]() ![]() In this example, the relevant version is 1.2 but the schemaversion could also specify 2004 2nd Edition, 2004 3rd Edition, or another edition.ģ. Schemaversion: This tells us which version of the SCORM specification the course is compliant with. Schema: The manifest should contain this information to record which “SCORM schema” is being used. In reality, a course could contain hundreds of entries in the manifest.ġ. It contains just a single module and enough sample files to illustrate our discussion points. While we’ll discuss some of these now, it’s worth noting that this is a basic example. ![]() The file contains key information for your LMS to interpret. The XML file will look something like the example below. That can cause a lot of confusion for SCORM creators as an LMS won’t import the zip files.Īs the imsmanifest.xml name suggests, the file is in XML format. If the manifest isn’t there, the file goes against SCORM specifications. When your LMS tries to import SCORM content, it will look for the manifest in the root of the zip file. One important point to note is that the manifest must exist in the root of the zip file, and nowhere else. Remember that the zip file contains an imsmanifest.xml file. And you can explore a number of other examples here. This particular SCORM package was copied from the Rustici Golf example you can find here. You can download the zip file for this sample course here and explore as you need. The imsmanifest.xml coupled with that “SCORM API magic” is what makes this zip a SCORM package. As those with experience of SCORM and the Rustici Golf course will know, the “shared” folder contains all the SCORM API magic that allows the course to communicate with an LMS when it’s launched. It’s just a folder containing html, images, and javascript files, which means it contains online content that can play in a browser to be viewed by learners. As you can see, there’s nothing particularly ‘SCORM’ about it. In this simple example of a SCORM course, the screenshot shows the contents of a “Playing” folder – marked 2 in the screenshot. Complex courses could contain many folders and additional folders within this hierarchy.ģ. This is an accurate but simple example of the folders and structure of a SCORM zip. The screenshot shows the imsmanifest.xml file sitting in the root of the SCORM package zip.Ģ. Here’s a screenshot of typical zip contents that have been opened for viewing:ġ. These files allow your course to communicate with a SCORM compliant LMS that understands the same SCORM protocols. These are called the SCORM API communications and logic files, they’re at the heart of why the package can be defined as a SCORM course. Your authoring tool will also have included files that it didn’t create that are SCORM specific.The imsmanifest.xml serves a similar purpose – it details the contents of the zip package – but we’ll get into the nitty gritty of why that matters later on. For example, an aircraft’s manifest file would detail the names of passengers, where they’re seated in the aircraft, the weight of the cargo in the hold, and a wealth of other information about the aircraft and its “contents”. This manifest file specifies the contents of the zip. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |