• 
  Please support me in the 2010 Ride to Conquer Cancer - last year we were able to raise $6.9 million for the Alberta Cancer Foundation - hopefully we can raise even more in 2010!

  ---

• Search for:

• Pages

  • About
    • Colophon
    • Contact
    • Curriculum Vitae
    • Presentations
  • Archives
    • Recent Comments
    • Shared Items
  • Asides
  • Photography
  • WordPress
    • Akismet Credit Inserter
    • Post Revision Display

• Categories

  • aside
  • digital photography sessions
  • fun
  • general
  • photography
  • work

• Blog under the Creative Commons Attribution 3.0 License
  

Back in ‘98, when we started implementing AICC interoperability into our LMS at DiscoverWare, the specifications were rather incomplete, and the documentation was rough.

They’ve been working on them pretty intensely, and they’ve expanded to cover a lot of new ground.

It’s gone much farther than just metadata and content packaging. I’ve been reading through the Learning Design specification, and it’s kinda like a glue that holds all of the other specifications together. It seems like it’s quite an intelligent approach, pulling in various specifications wherever appropriate.

Here’s some of the useful specifications coming out of IMS:

• IMSLD – Learning Design: A kind of glue that provides a framework for integrating various other specifications into a meaningful system


• IMSMD – Metadata: For providing descriptive metadata, as used to define learning objects and assets.


• IMSLIP – Learner Information Package: Used to describe all aspects of a learner/user/administrator – personal information, history, progress, contact info…


• IMSCP – Content Packaging: Used to aggregate learning objects into sets, for use in courses or presentations.


• IMSQTI – Question Test Interoperability: Describe components of a test, as well as their tracking and assessment data.


• IMSDR – Digital Repository: Best practices etc… for communication between distinct and separate repositories.

Comments