Re: XML Only CMS?

Good point.  However, if the CMS allows you to validate input, and the 
presentation templates are fully tested, you can be fairly certain that 
valid xml will come out the other side.  If this is not enough, you can 
add a process to validate the output after publish.  I guess the 
efficiency of this design largely depends on the schema.  If you can 
wrap much of the user's input in CDATA and the tag attributes have a 
limited number of possible values (so you the user can select with a 
dropdown list rather than free type), this design might work easily.  
Otherwise, you may need to do lots of regex to clean up the users input 
to ensure no XML breakage occures. 

Dominic Cronin wrote:

>Agreed - pretty much any CMS can emit XML. Whether this is sufficient or
>appropriate for everyone is more of an open question. In this case, the
>requirements specifically mentioned XML schema validation. 
>
>It's easy to envisage a situation where other business systems need to read
>and write XML that is known to be valid with respect to a given schema or
>schemas.
>
>Dominic Cronin
>
>-----Original Message-----
>From: Seth Gottlieb [mailto:sggottlieb-/[email protected]] 
>Sent: 04 November 2004 22:50
>To: [email protected]
>Subject: Re: [CMS] XML Only CMS?
>
>  
>
>>We need a CMS system to handle our xml files only.
>>    
>>
>
>I think you can do this with any CMS that allows the
>user to create structured content (that is, entering
>content attributes, such as "author," into discrete
>form fields), and has a templating mechanism that puts
>content into markup.  The only twist is that you
>program your presentation templates to write XML
>rather than just HTML.  It does not matter what format
>the repository is in as long as the output is XML.   
>In fact, it is even better if your system does not try
>to store the content in the same XML schema that the
>client system requires.  That way, when you change
>your formats, you don't have to go back and edit all
>your content assets, you just change the template and
>republish.
>
>I think that Bricolage or Interwoven TeamSite would be
>particularly good for this use.  
>
>Best,
>
>Seth
>_______________________________________________
>cms mailing list
>[email protected]
>Subscription controls:
>http://lists.cms-forum.org/mailman/listinfo/cms
>Netiquette FAQ and related CMS lists - [cms-forum], [cms-pr],
>[contentmanagers], [cmpros]
>http://www.cmsreview.com/NetiquetteFAQ.html
>
>  
>