When referencing versioning, there are two areas of versioning to consider; 1) document versioning and 2) content model versioning. Document versioning is addressed and resolved in Issue eTMF-4. Content model versioning applies to management of content model versions. Content model version numbering format will follow the MajorVersion.MinorVersion approach to Content Model Modifications, as outlined in the 2/17/14 meeting slides and minutes. The OASIS eTMF Standard will have a published content model that uses a version number specified as 1.0 or 1.1, etc. Organizations can create organization specific versions of their content model ontologies by using the W3C OWL2 standard tag, VersionInfo. Organization specific information can be added to a content model. Since we are using W3C OWL to model content models, W3C has built-in support for versioning systems through use of the VersionInfo tag. The content model version number will have a format of majorversion.minorversion.organizationversion, where organization version will incorporate the following text: organization domain name. [versioninfo] . For example, any leaf or element of the content model could contain the organization specific version number as follows: 1.2.pharmacorp.com.1 In this case, the major version of the content model is 1, minor version is 2, and organization specific info for the content model is pharmacorp.com (domain name of the org), and 1, version one of this specific content model. Note that there can be additional dot-notation version numbers after the domain name to indicate versions of specific elements in the content model tree. Outside of the content model version numbering policies outlined above, Applications will determine how content model versioning will be managed and implemented