The Timeliness of SCORM 2.0 Discussions
Last Friday, I submitted two white papers forged with considerable ideas and suggestions from professional colleagues (Tom King), fellow professionals (Ethan Estes and Steve Flowers), and new colleagues from around the world (Martin Ebner).
Like Philip Hutchinson, I began the efforts with a serious attempt to produce a formal and very “serious” (read: academic) body of work. I additionally tried to take an informal, yet collaborative approach to writing the papers through the use of Google Docs. Like Philip, even though I turned in my papers on time, I don’t know that I got it all written exactly as I want to express my thoughts. Without ample review of the papers prior to their submission, I must accept that they’re conversation starters (hopefully), and that the discussion that should follow will take the initial ideas proposed and give them life and definition.
My papers are here:
- SCORM 2.0 Content Authoring Standards & Services
- Engagement, Collaboration and Community in SCORM 2.0
Ironically (or just coincidentally depending on whether you’re a fan of Alannis Morrisette or not), the transparent and completely open formation of what is to become SCORM 2.0 is happening at the same time as we learn about the dissolution of the ECMAScript group and the CSS-WG in the W3C. Plenty of good discussions of what went down here, here, here and here.
It’s pretty crazy to me that all the reasons being cited as to why these two groups fell apart all boil down to similar root causes:
- Trying to take on too much by doing innovation by committee instead of codifying exemplars of best practice.
- Working behind closed doors.
- Losing the “vision.”
At least, that’s how I see it.
Managing that level of response is proving to be challenging. The rewards, however, are so worthwhile. Each member of the Program Committee has a “Bird Dog” — which means we have a paper we’re going to actively promote and raise awareness to. I have ten (they’re small ones — like a page each). That also means ten times the discussion (suckas!!!)
We’re going to swipe at these white papers by tagging each of our bird dogs to help us wrangle them into the requirements that will ultimately come together at the SCORM 2.0 Workshop in October (see the LETSI site for details — I’ll be there). The first stab we’re going to take is tagging a paper as proposing a SCORM “evolution” or “revolution.” It may seem simplistic, but we have to get a handle on the wide scope of ideas by starting to categorize them.
- Evolution - SCORM looks like relatively the same animal as before. It has the about the same scope and it solves very similar problems, but perhaps in new and innovative ways.
- Revolution - SCORM is a new beast entirely. It tackles new problems, increases the scope or completely changes the conceptual model.
Technorati Tags: scorm 2.0, letsi, standards, css 3, ecmascript 4, w3c, white papers, transparency