Slashdot Mirror
Should Open Source Content Management Interoperate?
bergie writes "Advogato is running a thought-provoking article on whether open source content management systems should interoperate. This is a big question involving social issues inside the projects, but also promising huge benefits to developers deploying open source CMSs and to desktop projects like Mozilla, OpenOffice and Xopus wishing to connect with a collaborative backend. This discussion will also be a major topic on the upcoming OSCOM conference."
The DoD (Dept. of Defense) wants various CRMs for teaching courses online (WebCT, Blackboard, etc.) to be SCORM compliant to allow transition of teaching/content modules.
/. tradition, I have not read the article.
Of course, in the finest
(BSD's 4.2 TCP stack is in both windows 2000 and WinXP). Please correct me if I am wrong.
That is a fallicy. The truth is that the original version of WinNT contained a third party TCP stack; it turned out the people they bought it from stole it from BSD. The stack was then re-written.
The credit to the regents of the Univ. of Calif. in the Windows readme file is for the simple tcp/ip unix utilities (ftp, telnet, finger, etc) which are bsd code to ensure compatibility and similarity for unix folks when using the commandline on a windows box.
Yes, WebDAV is a protocol commonly-used by many content management systems (commercial and open-src)...See http://www.webdav.org
WebDAV really has nothing to do with the "Web" except that it uses the HTTP protocol. I would not consider that a "web-based" solution. In other words... WebDAV has nothing to do with a browser and everything to do with HTTP.
Postnuke also has an implementation of the blogger api, allowing all those little win32 desktop apps (as well as PDA, cellphone) access to your postnuke site. I personall think postnuke is the way, with tons of modules available. I'm waiting for PostSHOP to get going again (there was a shopping cart for older versions of pustnuke, but it was deemed unstable/insecure, iirc). With just about as many themes available for postnuke as there are for KDE, and even a template generator for the upcoming 8.0 release, that's where I see the future. You can check out my somewhat new site (nice theme) at bhsx.yi.org. I'd say it took about 20 minutes to setup and about half-an-hour's worth of content so far. Super simple.
put the what in the where?
We've designed a system similar to what you are thinking about. Where I work we are beginning to use ZOPE for content management. We have some content that needed to be shared between multiple front ends. What we've done is used ZOPE to store static content, and then used ZOPE with a relational DB to store individual field data via a web form. This way the other front ends can pull the individual fields that they need without accessing ZOPE and ZOPE can use the same data to generate XML. It can then be transformed into other XML, XHTML, WML, PDF, TXT, etc. That's one of the main benefits of XML when it's partnered with XSLT.
"Do not be swept up in the momentum of mediocrity." - anon
I'd suggest that people who are interested in syndication standards check out the Information & Content Exchange (ICE) standard, at http://www.icestandard.org. They're working on a version 2.0 of the standard based on SOAP amd XML Schema (version 1.x is based on XML and a DTD). There's a web site and mailing list for interested parties...