Basically, SCORM means two things for course developers. First, there is a Javascript API that let's you communicate with the server. You call functions like LMSInitialize()/LMSFinish() to tell the server the student has started/ended the course, and LMSSetValue()/LMSGetValue() to set and retrieve tracking/user data. The second part is the manifest file which is an xml file stored at the root that defines the course structure, lists all resources (text, images, etc) and can go as far as defining the entire organization/navigation of your course (a part I'm not too fond of). This is all very specific to eLearning and honestly, I've never seen a "standard" quite like this. I can see some of the reasoning behind it but there are definately pieces that go too far. I like standards that don't impose. And why use Javascript? Why not go XML POST requests to the server directly? So this isn't a CMS standard. It is really only for eLearning. SCORM can be defined in our speak as a standard for communicating between a published site (post-CMS) and a portal.
a. -----Original Message----- From: Austin, Darrel [mailto:[EMAIL PROTECTED]] There isn't a CMS 'standard', is there? -Darrel -- http://cms-list.org/ more signal, less noise.