Why Mashups Make the LMOS
Jan 30, 2006
Commentary by Stephen Downes

I have been sort of sympathetic to the concept of the learningmanagement operating system (LMOS) because, after all, the concept includes things that I favour: distributed resources, user access to the underlying system. But I began to falter when Michael Feldstein said "We don't just want to offer many different affordances. we want to orchestrate them." And following his link to Bernie Durfee has sketched out a first use case implementation sent me over the edge. I'll say it bluntly, and apologize later: this is the most ridiculous thing I've seen. Durfee is describing what the rest of understand as 'upload a file and base a discussion thread on it'. Something I did right here in about 10 seconds today. But he requires J2EE containers, portlet containers, service integration agents, native Java interfaces, a whole mess of stuff. Ridiculous. Absurd! That's it - if that is what is meant, toast the whole LMOS concept. Total: 27
[Direct Link] 33402
Comments


Your Comment

You can preview your comment and continue editing until you are satisfied with it. Comment will not be posted on the until you have clicked 'Done'.



Enter email to receive replies:

Your comments always remain your property, but in posting them here you agree to license under the same terms as this site CC By-NC-SA. If your comment is offensive it will be deleted.

Automated Spam-checking is in effect. If you are a registered user you may submit links and other HTML. Anonymous users cannot post links and will have their contents screened - certain words are prohibited and comments will be analyzed to make sure they make sense.