<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2523" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>Hi
list:</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>This is a possible
new feature, for discussion.</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>Well, version 6 most
beautifull feature (for me) is the definition of the content structure, using a
'simple' xsd schema. The rest of the content management process (content life
cycle) is done by the opencms system.</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>This is wonderfull
if you have a very well defined content domain. But, i fear this is not the
standard on our web projects. Example:</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>The content is
"Product for sale"</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>The marketing guys
want new data, "rating of the product by the users" to be
introduced.</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>Then, with the
actual content definition system and tools, you could modify the xsd, or
introduce another object type, "Rating" with a link to the "Product for sale".
This is a tricky AND slow solution, but could work.</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>The feature is:
Provide a flexible way of editing the content schema after the content
definition and publishing. It could be an script that reads all the content xml
files and checks for correctness, GENERATING the empty fields, possibly
assigning a default value, configured by the admin.</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>It could be more
simple to have a "check xml" script, that lists all the xml content that does
not validate against its schema (showing a link list so you can correct all the
content from that list).</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial size=2>What do you think
about it ?</FONT></SPAN></DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=857180912-07122004><FONT face=Arial
size=2>Jorge.</FONT></SPAN></DIV></BODY></HTML>