Source control for requirements documentation

[jbeatty]

Has anyone given thought to a good source control system for requirements documentation (or any documentation)? Specifically I'm talking about a system that would not be used for source control of code.

I found this link that compares source control systems by high-level features - http://better-scm.berlios.de/comparison/comparison.html

My first impression, which is confirmed by skimming the feature list in the link, is that the requirements are far more complex for managing development work than for documentation.

Basic requirements off the top of my head, in no order:
-Backs up work somewhere other than individuals' computers
-Central repository for team to get the latest working drafts
-Store past versions of documentation
-Retrieves past versions of documentation
-Label final releases of documentation (i.e. baseline state before development, launch state)
-Easy to use for non-technical users
-Merges changes between versions (not sure this is actually a good idea, maybe just compares versions)
-Faciliates multiple authors working on a document without stepping on each others changes (maybe locks versions out for edit, maybe displays a version is changed from what is on local machine)

Is there a good simple source control solution that is easy to use and handles the very basics for documents (various formats)?

[MTalbot]

I'd add to your list of features "Ability to require auditing".

I want the ability to submit a revision to the source control, and to have someone (or several people) audit that revision against the baseline and either reject or accept it. This basically forces a second set of eyeballs to take a look at anything that's going into version control.

I like the features of MKS Omniworks (now Source Integrity Tool), but the user interface is (or was) incredibly non-intuitive. Developers who force users to type "s*`*`R*`t*`l*" because they simply couldn't conceive of needing more than 14 characters to specify a path and filename should be shot.

[jbeatty]

I find that usability is actually a block for non-technical people using source control, so that tool doesn't sound so ideal to me. :)