The problem, of course, isn't the software. It's the use of the software and the process of organization. First, the world of Zope falls into the same trap as the rest of content management. It thinks we are back in the days of mainframes. Most content management approaches an application by forcing everything to come live in one place, with few meaningful connections to information lying elsewhere.For the problem isn't lack of content.…
Boy, there's lots of good content on all the sites in the world of Zope. Unfortunately, we rely on a center that is in decline. I've become curious about the opportunity: could we "practice RDF" to bootstrap a semantic community and avert the problems of a cathedral-approach to community information?
Problems I have with the FloodRiskNet web site, built on Zope and Plone. We try to build a community around a centre, but the members of the would-be community are also members of other communities, thriving or would-be, with different centres.
Added to which, the support for information management in Zope -- and all other content management system which I have come across -- suck.
I'll try in future posts to put some specifics behind the meaning of both "semantic community" and "bootstrapping". Both are terms that I've written lots of notes about and talked about with others. As with everything regarding the Semantic Web, getting from stratosphere to terra firma is the challenge.
I wait with baited breath …
Comments