<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Hessiansx4, you might also want to look at this forum: http://tech.groups.yahoo.com/group/framemaker-dita/messages</span></div><div><br><span></span></div><div><span>As
for naming conventions, we name our files with a letter based on the
topic type, all lower case, only underscores to separate "words", and
use a "phrase" that is like an index term according to the content of
the topic, not what manual it goes in. For example:</span></div><div><br><span></span></div><div><span>concept: c_widgets_description_american, c_widgets_description_canadian<br></span></div><div><span>reference: r_widgets_parameters</span></div><div><span>task: t_widgets_parameters_setting</span></div><div><span>glossary: g_widgets, g_thingmabobs<br></span></div><div><span>conref: cr_widget_daily_statistics (that might be a conref for a report
name...we also use conrefs for product names)</span></div><div><span>map: m_productname_users_guide_print</span></div><div><br><span></span></div><div><span>We
name ditaval files the same as the corresponding map file and store
them in the same folder with the maps. For example,
m_productname_users_guide_print.ditaval.<br></span></div><div><br><span></span></div><div><span>We don't use a CMS, so my (small) team shares a folder on my computer. In it we have subfolders to store different topic types:</span></div><div><br><span></span></div><div><span>concepts</span></div><div><span>conrefs</span></div><div><span>glossary<br></span></div><div><span>graphics</span></div><div><span>maps<br></span></div><div><span>references</span></div><div><span>tasks<br></span></div><div><br><span></span></div><div><span>It's
difficult to answer your open-ended questions just off the top of my
head at the moment (it's still morning here); however, other points you
might
want to examine and plan out ahead of your transition are:</span></div><div><br><span></span></div><div>o What kind of output do you need?</div><div>o Are you using a CMS? If not, how will you manage/share your DITA files?<br>
o If you are using a CMS, does your CMS provide processors to create those outputs or do you need plug-ins?<br>
o Do you have developer resources, or are you very technically inclined?<br>
o What is your budget like?<br>
o Do you have support from above?<br>
o How large is your tech writing department?<br>
o How much R&D time do you have to develop your projects (including setting up your tools to create your required output)?<br>
o Will you have to create content/product while you are converting to DITA?<br>
o Do you need to support other source format besides DITA?<br>
o How complex will your DITA be, and do your tools support DITA 1.2 or only 1.1?</div><div><br></div><div>I can recommend the following software:</div><div><br></div><div>WebWorks
ePublisher: Handles DITA beautifully, and if you need to create output
while you're transitioning, you can mix DITA, FM (unstructured), and
Word providing you have bought all three adapters (www.webworks.com).<br></div><div>Suite
Solutions' Ditaval File Generation Utility and DITA Packager Utility:
free, but invaluable
(http://www.suite-sol.com/pages/resources/downloads.html)</div><div>Mif2Go
or Dita2Go: for conversion from unstructured to structured. We also use
Mif2Go to convert FM files to Word for developers and customers.<br></div><div><br></div><div>If you have specific questions, I'd be happy (to try) to answer them for you off forum, too.</div><div><br></div><div>Hope you find something helpful in that,</div><div><br></div><div>Nadine</div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> hessiansx4 <hessiansx4@yahoo.com><br><b><span style="font-weight: bold;">To:</span></b> "framers@lists.frameusers.com" <framers@lists.frameusers.com><br><b><span style="font-weight: bold;">Sent:</span></b> Thursday, November 3, 2011 2:49:05 AM<br><b><span style="font-weight:
bold;">Subject:</span></b> DITA file naming conventions<br></font><br><div id="yiv686036512"><div><div style="color:#000;background-color:#fff;font-family:verdana, helvetica, sans-serif;font-size:10pt;"><div style="">Hello All! My company is in the process of transitioning from FM8 unstructured > FM10 DITA and are discussing file naming conventions. Have any of you had a similar experience (transitioning to DITA)? Any caveats you want to share about the process (what worked/what didn't)? How about <var id="yiv686036512yui-ie-cursor"></var>file naming conventions? Any and all suggestions are welcomed!</div></div></div></div><br>_______________________________________________<br><br><br>You are currently subscribed to framers as <a ymailto="mailto:generic668@yahoo.ca" href="mailto:generic668@yahoo.ca">generic668@yahoo.ca</a>.<br><br>Send list messages to <a ymailto="mailto:framers@lists.frameusers.com"
href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.<br><br>To unsubscribe send a blank email to<br><a ymailto="mailto:framers-unsubscribe@lists.frameusers.com" href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a><br>or visit <a href="http://lists.frameusers.com/mailman/options/framers/generic668%40yahoo.ca" target="_blank">http://lists.frameusers.com/mailman/options/framers/generic668%40yahoo.ca</a><br><br>Send administrative questions to <a ymailto="mailto:listadmin@frameusers.com" href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>. Visit<br><a href="http://www.frameusers.com/" target="_blank">http://www.frameusers.com/</a> for more resources and info.<br><br><br></div></div></blockquote></div></div></body></html>