ADL Summarizes Next Generation SCORM Requirements

ADL, through a Broad Area Announcement (BAA) with Rustici Software, is pleased to present a compilation of the community requirements for the Next Generation SCORM (Sharable Content Object Reference Model). This White Paper translates a variety of technical and non-technical requirements that were collected and voted on as a part of the BAA outreach to the ADL Community. The result, although somewhat technical in nature, is a unified vision of what Next Generation SCORM should be. ADL, following the community needs, will strive to make the Next Generation SCORM:

  • Track diverse user learning experiences such as social media, mobile learning, games, simulations, and mixed modality exercises.
  • Move beyond the single-learner model to allow team-based exercises, collaboration, and direct instructor intervention.
  • Eliminate out-of-date technology practices such as the idea that all content needs to fit into a “package”.
  • Improve or eliminate the content sequencing and ineffective requirements.
  • Include tools, guides, and best practices to make the learning curve for Next Generation SCORM easier.
  • Provide clearer instructions and more efficient testing to make content work across systems.
  • Allow content to function in situations where access to network infrastructure is limited or intermittent.
  • Provide a means to expose user data to instructors while keeping assessment data secure.

We urge you to be involved in the development of Next Generation SCORM by following updates on ADLnet.gov and participating in ADL activities.

Tags Android Deployment, CMI 5, Content as a Service, Game Engine Integration, Learning Record Store, Legacy Content Wrapper, Next Generation SCORM, Run-Time Web Service, SCORM, Tin Can, tla | January 31st, 2012 | Posted in Announcements |

  • Pingback: Anonymous

  • Pingback: ADL Summarizes Next Generation SCORM Requirements | El Aula Virtual | Scoop.it

  • Pingback: Documentation | Pearltrees

  • John Plante

    SCORM should allows the integration of web services in order to prevent security holes. From what I’ve seen with Tin-can so far, the same vulnerabilities seem to exist. For example, there should be a web service quizzing API that delivers quiz questions and potential answers only. I’m working with a SCORM generation tool and already found a few places of concern when trying to deliver scores to the server. I have already seen a place where the answers to matching questions are easily discernible by viewing an XML file. I’m sure if I spend more time with the product, I could figure out how to discern quiz answers. Scoring should occur on a server, not only the client. Perhaps there should be 2 levels of SCORM content: server level security where the security of the quiz is paramount and client level security where SCORM can exist stand alone and where quiz scores are meant solely as a learning tool for the test taker and not as a means of certification. There could perhaps be a third level where a user can take a quiz in a disconnected manner without receiving a score but then receives a score once the client syncs up with a server (this could even by done via email).