<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div class="c-ReadMessagePartHeader"> <div class="t_hov MsgHover MsgPartGradient ia_hc Expanded toggleExpandMessage" data-link="class{fromContainerClass:IsBodyExpanded Collapsible}"> <div class="ReadMsgFrom FloatLeft">I think Rick is correct. Think of building small xml docs with a particular need in mind to get an idea of what structure is about. The infrastructure behind supporting a small xml doc is the same as for a large document (only with fewer of each of the parts that have to be defined in things like the DTD and the EDD). My first xml exploration involved data in a spreadsheet exported to tabbed text and then wrapped in xml tags. The problem then was to display the data elements in a document. <br><br>Craig<br></div> </div> </div> <div class="ClearBoth"> </div> <div class="ClearBoth"> </div> <pre>-------------------------------------<br>Hi, I am going to offer a contrary opinion. I wouldn't start with DocBook,<br>DITA, or any existing applications. I would create a simple, custom<br>application to get my feet wet. I do this when I train clients, even if they<br>are using DITA, etc. It helps them to digest the concepts with a small<br>application; then they can figure out how to get around in larger<br>applications.<br> <br>Rick<br> <br>Rick Quatro<br>Carmen Publishing Inc.<br>585-366-4017<br>rick@frameexpert.com</pre> </div></body>
</html>