Abstract
Nearly every commercial and open-source Web content management (CMS) package claims to be XML-compliant, and by now most do indeed use XML in some way. However, different CMS packages employ XML in different ways, and variations in archictecture can be significant for a potential CMS adopter.
For example, some systems store XML as flat files, others as an abstract overlay on top of a relational database (both approaches have advantages and disadvantages). Some packages can export XML from a content repository, but not natively import it. Fortunately, a significant body of experience is emerging that allows us to analyze results and draw lessons learned.
This session will examine some of the common approaches to leveraging XML in CMS applications and try to extract some general trends. Then it will suggest some best practices for implementing XML in Web Content Management projects and identify possible additional technologies that might be required for a complete solution.
The session will draw on analysis of major CMS implementations as well as vendor-neutral evaluations of leading technologies.
Keywords
Table of Contents
CMSWatch -- (www.cmswatch.com). Industry portal for CM products and practices
CMSWorks. CM consulting and training
Tony: tbyrne@cmswatch.com
12-year Internet veteran
Automate Web Publishing Process -- More, Better, Faster. Devolve, authority, accountability, control to actual content experts; separate content / presentation.
Maximize the Value of Structured Content. Re-use atomic content chunks across sites, channels, media.
CMS buyers enticed by content re-use (no.2)...
...But in this economy, they are buying for automation (no1)
Vendors are listening, esp. in the expanding mid-market
XML support is often "bolt-on"
"Pure" XML CMS vendors still consigned to niche markets
Everyone can dump ASCII
You'll see a lot of XML config files
Where differ:
XML storage (native or otherwise)
Transformation capabilities and tools
Standards (ICE/RSS, SOAP/WSDL, etc.) baked in.
Intelligent management of XML documents as XML documents
Programmatic access to XML nodes
Surprisingly little XML support
XML often pushed to Data / API layers
You could build with components (Xalan, Cocoon, AxKit, etc.)
Midgard: None
RedHat CCM: Yes (Oracle), but problems
OpenCMS: Yes, Sprechenzie Deutsch?
Zope: Its very own OODB...
Re-usability is challenging
What is good for the organization can mean more work for its employees
Analytical Challenge
Developer's challenge
Structured Authoring
CMS pendulum swings back towards value (from efficiency)
Web Services drives new business cases
"New Covenants" between enterprise and employee about maximizing content value
Yawning gap between page designers and XSL closes
![]() ![]() |
Design & Development by deepX Ltd. 2002 |