David suggested in his opening comments yesterday that "content is infrastructure." He was (I think) meaning to imply that content is an enabling platform, and that if a robust library of open content is available, that individuals and groups will be able to build new things from that library. Things that can't be predicted by the librarians and publishers. Things that are evolutionary and revolutionary. I completely agree that having freely available and reusable content is an extremely important factor in promoting education and community programs, especially in regions without the resources to build all content from scratch.
But, the "content as infrastructure" analogy doesn't sit well with me. Infrastructure is stuff like electricity, plumbing, roads and communication networks. Infrastructure's value is that you don't have to think about it - it's Just Thereâ„¢, and is "always on". You flick a switch, and don't need or want to think about the electrical infrastructure that heats up the filament in the bulb. You flush the john, and don't need or want to think about the water supply and sewage infrastructure. Hopefully, you won't have to.
But - content is one thing that you need to think about. It can't be pushed so far down the stack that it becomes a mindless and invisible component, akin to electricity. Content needs to be mindful, contextual, active, and interactive. It's not just a series of bits to be transported via TCP/IP (which could be considered infrastructure) - it's the context for a conversation.