Lately RSS has been on my mind a lot. I’m excited about the possibilites it opens up to us with regard to syndication and consumption of Web content–and I think there is still a lot of unchartered territory out there. In particular, I’m spending a lot of time thinking about how RSS could be a transformative power in teaching and learning.
It seems to me that about five years ago there were a lot of people talking about “push delivery” of content–or, content that can be deliverd to a user without him/her needing to go out and seek it. At the time, however, I think there were too many technology hurdles to be overcome to really make this concept a reality. Now, with the development of RSS and the growth of broadband (at least in corporate/campus environments), push delivery seems like much more of a possibility
And all of this makes me think about how RSS could be used to “get” content to students in more meaningful ways. I should admit, that I didn’t really start thinking along these lines until I came across this post by Will Richardson over at weblogg-ed (and he was actually summarizing/reflecting on a post by Tim Wilson on ETI–oh, those connections. . .) Both of them are talking about the potential of the encolsure tag in RSS 2.0 to deliver all kinds of content. Right now the emphasis is on podcasting, but really, the enclosure tag can point to any kind of file–as long as the client application knows what to do with it.
Yesterday, I had a chance to talk with our Web director here at UMW about RSS and the enclosure possibilities. We’re getting ready to launch a portal at the University, and our Web team has built us this spiffy tool that will allow users to create custome RSS feeds for getting content into that new environment. Among other things this “feed generator” will let you read multiple existing RSS feeds and then turn them around in a new, aggregate feed, containing items from multiple sources. You can also use the generator to create “custom” items (links to Web sites, resources, enclosures. . .)
Anyway, we got to talking about how there is no way to natively consume enclsoures in the portal environment–if for no other reason than there is no “place” to put the content that the enclosure is pointing to (much less a portal-enabled application that can handle enclosures). But what if. . .
- an application channel existed for the portal that could consume rss feeds with enclosures and
- that channel had access to some kind of server space that “belonged” to users and
- that application couuld download enclosure content into that space and
- maybe in doing so the application could “organize” that content in meaningful ways (based on custom XML tags that we determine?) so
- students could have a virtual drive for learning content that would be automatically downloaded and organized according to course, discipline, project, etc. and
- maybe we could even build other application channels that could display/deliver certain kinds of content within the portal (I’m thinking in particular about podcasting, here–I’ve seen modules for open-source CMS/portals that allow for playing of MP3’s within those environments. Why not in our own environment?).
Ok, I know this sort of a pipedream. But if you think about what RSS is–just an XML file with information about where content is that can be “customized” based on our needs and can then can be consumed in any number of ways depending on the application available, the possibilites seem endless. And, might I say, they start to blow the courseware world wide open. . .