Version Numbering:
Version numbering is very common amongst authors, and a variety of systems are used by individuals. Version numbers can be used by content creators to indicate the relationship between related objects. Using schemes such as Vx.y can also differentiate between major and minor releases.
For an example of a numbering system, please see here: http://en.wikipedia.org/wiki/Software_versioning
Note that if multiple authors are working on a particular object the versioning can branch into different lines before coming back together.
Version numbers are also common in computing applications, and many people use the Subversion package to control their versions. The framework includes an introduction to such packages in the Content Creation Section.
Pros:
- Version numbering is very easy to follow if a system is used consistently.
- Works very well for authors working on their own.
Cons:
- It would be difficult to impose a consistent version numbering system - a major change in one authors eyes may only be seen an minor by another.
- Having a version number does not describe the place of the object in a larger workflow unless all other version numbers are known.
Recommendations:
Content creators should seriously consider using a uniform,
consistent numbering system. If such a system is used, it is crucial to
stick to it and not create duplicate version numbers for separate
versions.