Skip to content

links for 2009-04-03

  • Content developers who are concerned about SCORM data integrity can take some actions to mitigate this vulnerability. Two ADL community members, Bill Blackmon and Jonathan Poltrack, have provided workarounds that may be applied to current and previous versions of SCORM content. Details for these workarounds can be found in SCORM Resources.

    http://www.adlnet.gov/Technologies/scorm/SCORMSDocuments/SCORM%20Resources/Resources.aspx

  • Over the last few days a new notice has appeared on the IMS Question and Test Interoperability webpage in place of the QTI v2.1 draft specification: "The IMS QTIv2.1 draft specification has been removed from the IMS website. Adequate feedback on the specification has not been received, and therefore, the specification has been put back into the IMS project group process for further work." This was clearly completely unexpected, not only for us at CETIS but also amongst a number of commercial and academic developers who have been working with the specification as can be seen by posts to the technical discussion list hosted by UCLES.
  • One of the most difficult things to do—even for simulation veterans—is to explain what happens in a comprehensive, technology-based business simulation to someone who’s never experienced one.

    If you’re faced with this challenge and are looking for ways to build consensus for simulations among key stakeholders within your organization, here are four tips for crafting a compelling business case: