<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
{margin-left:3.0pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt'><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Okay, I'll start from the assumption that DITA or Docbook as standards are the way to go if you don't want to spend all kinds of time and money on development. Of course changing to DITA or Docbook will cost time and money, too. Just less of both.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So which: DITA or Docbook<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>DITA is much more restrictive. The topics are formed from a very finite set of elements which your crew can learn to use adroitly with a little study and practice. Docbook has everything plus the kitchen sink thrown in as elements because it is meant to do, well, just about everything. For my money DITA makes a lot more sense, but your writers have to understand the conceptual framework and work within that relative simplicity. Don't imagine that you can do things like four levels of nested lists. Docbook, by contrast, let's you do just about anything you've been doing in unstructured FrameMaker, you just have to learn which of the many many elements lets you go ahead and do that.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>For my money, DITA is the way to go .<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Craig<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='color:#1F497D'><o:p> </o:p></span></a></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>rebecca officer<br><b>Sent:</b> Monday, July 08, 2013 2:06 AM<br><b>To:</b> framers@lists.frameusers.com<br><b>Subject:</b> DITA/docbook vs your own schema<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Does anyone know of a nice, clear list of what you save by using DITA/docbook instead of developing your own schema? <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><br>The content maps reasonably well to DITA, but not perfectly. I'm trying to figure out whether we're better off working within the limitations of DITA, or whether we should take the DIY approach. A clear list of what you save by using DITA would be really helpful.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Many thanks!<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'>Rebecca<o:p></o:p></span></p></div><p><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><br>NOTICE: This message contains privileged and confidential<br>information intended only for the use of the addressee<br>named above. If you are not the intended recipient of<br>this message you are hereby notified that you must not<br>disseminate, copy or take any action in reliance on it.<br>If you have received this message in error please<br>notify Allied Telesis Labs Ltd immediately.<br>Any views expressed in this message are those of the<br>individual sender, except where the sender has the<br>authority to issue and specifically states them to<br>be the views of Allied Telesis Labs.<o:p></o:p></span></p><p><span lang=EN-GB style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'> <o:p></o:p></span></p></div></body></html>