umber, letter, or date).
A version is defined using the MIL-HDBK-61A description.
ISO 10007-1995, 7.4.1 has only one reference to "revision", and no reference to "version":
...All change proposals should be documented and should typically include the following information prior to their submission to the CB:
- configuration item(s) and related documents to be changed, name(s) and revision status; ...
Since DOD-STD-2167A specifically addresses software development, it isn't surprising that "version" is used for a software variation:
3.34 Version. An identified and documented body of software. Modifications to a version of software (resulting in a new version) require configuration management actions by either the contractor, the contracting agency, or both.
But it is interesting that changes to DOD-STD-2167, as a document, are considered revisions:
6.5 Changes from previous issue. Asterisks or vertical lines are not used in this revision to identify changes with respect to the previous issue due to the extensiveness of the changes.
The IPC-257x standards for defining Product Data eXchange (PDX) files offers both revision (productRevision) and version (versionIdentifier) for parts, but only describes versions for electronic file attachments. While the IPC standards don't offer any distinction directly, revisions have somewhat superior standing; for instance, an item change history includes "oldRevision", "newRevision", "proposedRevision", "minimumShippableRevision" but there's no equivalent for versions. Likewise, (although we discourage it for other reasons) engineering changes are permitted to have revisions, but not versions.