e-Literate

Present is Prologue

Tag: Rob-Abel

  • The IMS Is More Important Than You Think It Is

    I have long argued that the development of technical interoperability standards for education are absolutely critical for enabling innovation and personalized learning environments. Note that I usually avoid those sorts of buzzwords—“innovation” and “personalized learning”—so when I use them here, I really mean them. If there are two fundamental lessons we have learned in the last several decades of educational technology development, they are these:

    1. Building monolithic learning environments generally results in building impoverished learning environments. Innovation and personalization happen at the edges of the system.
    2. There are tensions between enabling innovation at the edges and creating a holistic view of student learning and a usable learning environment. Integration does matter.

    To these two education-specific principles, I would add a general principle about software:

    • All software eventually grows old and dies. If you can’t get your data out easily, then everything you have done in the software will die with it (and quite possibly kill you in the process).

    Together, these lessons make the case for strong interoperability standards. But arriving at those standards often feels like what Max Weber referred to as “the strong and slow boring of hard boards.” It is painful, frustratingly slow, and often lacking a feeling of accomplishment. It’s easy to give up on the process.

    Having recently returned from the IMS Learning Impact Leadership Institute, I must say that the feeling was different this time. Some of this is undoubtedly because I no longer serve on any technical standards committees, so I am free to look at the big picture without getting caught up in the horrifying spectacle of the sausage making (to mix Germanic political metaphors). But it’s also because the IMS is just knocking the cover off the ball in terms of its current and near-term prospective impact. This is not your father’s standards body.

    (more…)

  • When It Comes to Content, Say “Yes” to Wrappers But “No” to Containers

    Scott Leslie has a good post up ruminating on the moving target of open textbooks which reminded me that I have long intended to write a follow-up to an exchange that he, I, and Rob Abel had in the comments section of a post a I wrote a while back. Scott lamented that the Washington State Board for Community and Technical Colleges was releasing its open course content in IMS Common Cartridge format, which seemed to him to be not so easily accessible or universally usable as one might like. I wrote in response,

    Fundamentally, I don’t believe in cartridges. I don’t believe in forking a copy of a digital resource and stuffing it into another system. It’s bad for a variety of reasons, including but not limited to the implementation challenges that Scott ran into with Moodle (although it’s fair to say that some LMSs handle CC import better than others). Common Cartridge made more sense 5 or 10 years ago, but it’s late to the game and is ultimately destined to be eclipsed by in-place APIs, including but not limited to IMS LTI. (By the way, I’m not so sure it’s such a good idea to let Google own our integration API either.)

    Unsurprisingly, Rob Abel, as CEO of the IMS, took issue:

    If there is agreement that CC helps with the issue of content in an LMS then, well in your scenario the content is inside the publisher “LMS” (or equivalent).

    Can I tailor it? Can I put things in there – like a syllabus – and get it out? If I’m the student and I create something in there can I get it out? Can I mix and match with other publisher materials? Can I archive that mixing for next term? Can I share what I did with my faculty peers who might want to learn from it? Can I create assessments in there and then use them somewhere else or just put them somewhere so that I can use them in the future?

    Common Cartridge – or something like it – helps solve those issues. Fits right into the topic of openness. But, most importantly, in the digital education age we need to make digital education easy for the faculty and the students. Otherwise there won’t be a digital education age :-)

    Perhaps a mixture of OER and publisher proprietary stuff might be a solution. IMHO, some stuff needs to be tailored, remixed, moved in, and moved out. Doesn’t matter whether it’s a publisher platform or an LMS. Faculty want their stuff. Students want their stuff. Publishers need to help them, not thwart them.

    I said that the binary choice Rob was offering up wasn’t the right one and promised to elaborate in a future post. Here, at last, is that response.

    (more…)

  • A New Article Out

    I’ve been so busy lately that I haven’t even had time to post notice that I have a new article published in ALT-N. I’ve been having conversations on and off with Rob Abel about ways to ensure that educational technology standards (and, of course, the educational technologies themselves) are more effectively informed by our developing understanding of best practices in online teaching and learning. More recently, I’ve been having somewhat similar conversations with Seb Schmoller, except in the context of ALT rather than IMS. Coincidentally, Seb sent me an issue of ALT-J that talks about the use of pattern languages to make sure that accepted best practices in online learning are more effectively informed by various cognitive and learning theories, and vice versa. (Longtime readers know that I have a fondness for notion of pattern languages and have even created a category on my blog about applying the concept to education.) As I read the article, it occurred to me that use cases serve a similar bridging function between software users/practitioners and software developers. If you could form a bridge between a pattern language of educational best practices and a body of use cases that describe how software could support those best practices, then you might really have something. Hence, the article.

    As usual, Stephen Downes as a few nits to pick.

    To begin with, he complains about the use of the word “praxis,” which he describes as “just the word ‘practice’ with an attitude.” It’s true that “praxis” is often incorrectly understood as and used interchangeably with “practice,” which is why I usually avoid using it. I chose to use it this time for two reasons. First, the authors of the article on pattern languages used it, so if I chose not to use it I would be creating an inconsistency in language which I would have to take significant word count to explain. More importantly, though, they had used it correctly. Praxis, properly understood, refers to the set of best practices that is empirically derived from practice (as opposed to being the practice itself). It is a kind of experiential-derived theory and is meant to be contrasted to more classical scientific theory. So principles of physics are theory while principles of engineering are (generally) praxis. Or, in this context, principles of education derived from cognitive psychology are theory while principles of education derived from teaching experience are praxis.

    His other complaint is…well…I’m not sure what it is. He writes,

    I’m uneasy with this – it’s hard to articulate why, exactly – but I don’t think software should be designed to ‘do things’ so much as it should be designed to ‘create capacity’. I know that’s not a very clear distinction. But it’s like the difference between ‘process’ and ‘creation’.

    He’s right about one thing. It’s not a very clear distinction. In fact, I have no idea what he’s talking about. The only thing I can think of regarding “creating capacity” is Don Norman’s concept of affordances. But affordances are entirely consistent with use cases. In fact, use cases are an excellent (and commonly used) way to ensure that your software is designed to “create capacity” in the way that users want.

    So I guess I’m still in the dark. If Stephen (or anyone else) wants to couch his criticism in concrete terms that are consistent with the…um…praxis of user-centered software design, then I’ll be happy to respond further.

  • Patents and IMS Common Cartridge

    A while back, IMS CEO Rob Abel was kind enough to comment on my post regarding the potential impact of patents on educational technology standards. As part of his summary at the end of the comment, he wrote,

    It’s difficult for Blackboard or any other vendor to “game” the standards process in IMS due to our IP policies. So, in fact the standards organizations are a great way to bring issues like this out so they can be known – and, in the case of standards, potentially go in a different direction if one organization’s IP is encumbering. The standards become the known ground that vendors must share without claims.

    While I appreciate Mr. Abel’s effort in sharing his thoughts, and while I am glad to hear his optimism, I’m afraid that recent history with technology patents shows that it is not so easy for standards bodies to protect themselves from abuse by aggressive patent holders. (more…)