Re: [generguide-devel] <xinclude> links

[Cameron S. <ca...@sh...>]

On Saturday 13 Sep 2003 9:53 pm, Sean Wheller wrote:
> If CVS is managing the files and their versions. Why
> add to the path with a
> version number? If a version is required, could it not
> be included in the
> file name. This way regardless of the file location,
> the version number will
> always be known.

I envisage that there will be multiple GenerRepositories.  Each repository 
will be independantly administered from each other, putting out their own 
releases of guides relevant to their area of expertise.  Each repository will 
issue releases which reflect updates.  Both new and old releases need to be 
accessable via the web by other projects.

So, if I am creating a Developer's Guide for the Linux Documentation Project, 
I may reference the Sun Java Coding Standards (maintained by Sun).

There are 2 types of guides I may want:
1. A guide that doesn't change over time.  I'm developing a product which is 
not going to upgrade it's toolset, so I want my Developer's Guide 
configuration to always reference Java 1.4 docs.  So I reference release 4.0 
of the Sun's GenerRepository.

2. A guide that always refers to the latest development practices.  So I 
reference the head release of Sun's GenerRepository.

Does this make sense?

-- 
Cameron Shorter              http://cameron.shorter.net
Open Source Developer        http://generguide.sourceforge.net
                             http://mapbuilder.sourceforge.net
                             http://geotools.org
Senior Software Engineer     http://www.adi-limited.com