[
Lists Home |
Date Index |
Thread Index
]
IMO, it depends upon what kind of processes to which you are applying
XML. If you are mainly applying toward technical documentation and
you already have a content management system (CMS) for your legacy
formats, that CMS should be a consideration.
If on the other hand you are looking at XML because you are going to
use it as part of the source code base for an application, then the
source code control system should be considered. (If you aren't
using a source code control system when writing applications, you
should be.)
A for-instance: when my client, a test automation team, decided to
document test procedures with XML, they integrated the new schemas
and scripts into an existing ClearCase source control system, and
managed their XML in it.
- Mitch
Pavel A. Sher wrote:
> Hello,
>
> Suppose, I am starting a new project containing xml documentation.
> That xml documentation will be processed by some tool which is able to
> generate documentation from source xml files in various formats. Is
> there any standard or preferable organization of catalogs for xml
> documentation projects?
>
> For example, are there any thoughts what is a good place for source
> xml files, dtd, xsd files, images and various binary files?
>
>
|