To be clear - preferring to manage content *as content*, instead of lossy extraction of domain entities is about preferring flexibility and independent evolution of systems. There's plenty of room for an argument that says RDBMS is suboptimal for managing content. And good luck with versioning or translation on top of relational databases while trying to manage the form and flexibility of the content over time. Yes, you can do it, but it's highly specialised and diffiicult work. Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fwww.dehora.net%2Fjournal%2F2006%2F08%2Fzope_java_content_repository_and_web_architecture.html
OpenKM is focused on creating a open source electronic document management system, that due to its characteristics can be used by great companies as well as by the small ones, as a useful tool in processing knowledge management, providing a more flexible