<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
For what it's worth, the DITA Style Guide recommends using names
that match the titles.<br>
<br>
It also recommends using the extensions .dita and .ditamap, instead
of .xml. That way, you have more control over which tool opens the
file, and you can distinguish the files from other xml files used in
DITA. <br>
<br>
On 2011-11-03 15:02, Roger Shuttleworth wrote:
<blockquote
cite="mid:20111103190232.32b1253a@mail.avbasesystems.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style>BODY{font:10pt Tahoma, Verdana, sans-serif}</style>
Hi Jim<br>
<br>
You make a good point about updating xrefs and related-links, as
well as ditamaps, when a file name changes.<br>
<br>
I have made good use of the map checking function in oXygen
Author. You open the map in Author, then run it through an
automated checking routine that will point out any problems such
as missing files or inappropriate href values.<br>
<br>
I sent a follow-up message to the original poster correcting my
recommendation to use folders named according to deliverables. I
meant to recommend using the product name, not the deliverable.
Different deliverables are created from a single pool of files,
using different maps; or perhaps using the same map filtered by
ditaval.<br>
<br>
Thanks for your tip about GUIDs too. I will look more into that.<br>
<br>
Roger Shuttleworth<br>
Technical Documentation<br>
AV-BASE Systems Inc.<br>
1000 Air Ontario Drive, Suite 200<br>
London, Ontario<br>
N5V 3S4<br>
Tel. 519 691-0919 ext. 330<br>
<blockquote style="padding-left: 5px; margin-left: 5px;
border-left: 2px solid rgb(0, 0, 255); margin-right: 0px;">
<hr><br>
</blockquote>
</blockquote>
<br>
</body>
</html>