Structuring a project (bis)

Subject: Structuring a project (bis)
From: "Claudine CHAUSSON" <claudine -dot- chausson -at- jwaretechnologies -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 5 Jan 2010 16:14:45 +0100

Hi everyone

First of all, I wish you a very happy and prosperous year 2010.

Then, I'm posting this message again as the first time I didn't get any
answer. I'm probably unclear in my explanations of the issue I'm facing but
I find it hard to explain it clearly as I don't have any idea on how to
solve it. Any help would be really appreciated. I'm interested too if you
have readings to suggest about projects structuring.


I have an issue with the structure of my project. I use DITA, Oxygen to edit
it, and ClearCase for version control. I output to pdf.

I?m writing the same manual for 2 different clients (but it could be for
more clients). Many topics are common, some are specific and some are of a
mixed type. I could use metadata to tag the information and then use DITAVAL
to include or exclude topics; it works well. But how can I do if I need to
create a manual for a new client and then another new one, and so on?
I figured I could use different folders and follow a structure similar to

- ManualName
  O Client1
    * Client1 Images
    *(list of files specific to Client1 + Client1 project + Client1 ditamap)
  O Client2
    * Client2 Images
    *(list of files specific to Client2 + Client2 project + Client2 ditamap)
  O Images         
  O (list of common files)

Is it feasible (and viable) to work like this? What about mixed type topics
(topics that are mostly common but the terminology, for instance, is
different)? How can I manage those? With DITAVAL? Variables (using conref
and not keyref as I'm using DITA 1.1)

Any insight will be appreciated.

Technical writer
JWARE Technologies

Mail/to: claudine -dot- chausson -at- jwaretechnologies -dot- com

Please consider the environment before printing this email.


Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Previous by Author: Re: A Better Technical Writer/Communicator Library
Next by Author: Re: Q1 2010 job market
Previous by Thread: RE: Q1 2010 job market
Next by Thread: Structuring a project (bis)

What this post helpful? Share it with friends and colleagues:

Sponsored Ads