Applications often require the ability to distinguish between different versions of objects in general. This Addendum applies this principal to ResourceSpecifications. The ResourceSpecVersion class represents a particular form or variety of a ResourceSpecification that is different from others or from the original.  The form represents differences in attributes and relationships (as well as methods and/or constraints in the system view) that characterize this particular ResourceSpecification, but which are not enough to warrant creating a new ResourceSpecification.<br/>Notice that a LogicalResourceSpecVersion doesn’t define any new (business) attributes of its own. This is because the purpose of this class is to be able to track LogicalResourceSpec objects separately from other types of ResourceSpecifications. <br/>Brief definitions of the attributes of this class are as follows:<br/>        • The resSpecRevisionName attribute defines the name of this revision for easy storage, retrieval, and querying<br/>        • The resSpecRevisionFormat attribute defines the specific format of this revision (e.g., 2.5.3a)<br/>        • The resSpecRevisionNumber attribute contains the actual value of this instance of this revision<br/>        • The resSpecRevisionReason attribute contains the reason for creating this revision<br/>        • The resSpecRevisionSemantics defines the particular semantics of this version, such as a minimum a description of the format of the revisionNumber<br/>        • The resSpecRevisionTimestamp contains the date and time that this revision was created<br/>        • The resSpecRevisionValidityPeriod defines the period of time for which this revision is valid<br/>The ResourceSpecVersionDetails defines the semantics of the relationship between ResourceSpecification and ResourceSpecVersion. Specifically, it enables an application to define which set of versions of the ResourceSpecification are appropriate for a given task.<br/>This relationship represents the set of versions of this ResourceSpecification. However, this class is not appropriate for this business view, and hence is not described in this section.<br/>