QDoc Specifications and Standards > QDoc XML Attributes > version
  
version
This attribute is specific to QDocs. It identifies the version of a QDoc schema to which a particular instance of that QDoc conforms, and is required at the QDoc root element level. Its format is _, where is the lowest major release of the QAD application product in which the QDoc is supported (for example, eB, eB2, QAD SE, or above for QAD EE), and is an incremented sequence number within that release starting with 1. Any periods in the release name are removed.
Example: The first version of an QAD Enterprise Applications QDoc that is developed to work with both the eB and eB2 releases would have the version eB_1, for both eB and eB2 users. If this QDoc were later enhanced only for releases QAD SE and above, the new version would be called ERP3_1, and could coexist with version eB_1 if QAD decides to support both versions concurrently. If the same enhancement were later retrofit to eB and eB2, the new version for the eB and eB2 releases would be called eB_2. Note that service packs are not treated as major releases for QDoc versioning purposes.
This versioning scheme allows multiple versions of the same QDoc to be supported concurrently for multiple product releases, while capturing in a natural way the relationships and compatibilities among the various QDoc versions and product releases. For custom or user-extended QDocs, QAD suggests that custom version designators be assigned as suffixes to the QAD-supported versions on which they are based (for example, eB_2_ABC_1 for the first customization developed by ABC Company). While all customized QDocs must be defined in a namespace different from QAD’s in order to avoid name-version clashes, customer-specific version identifiers help highlight their custom nature. See QDoc Namespaces.