Schema File Names and Versioning
Versioning is handled differently depending on the syntax specification in use. Refer to the appropriate section.Versioning for 1.1 Schemas
The XML schema files defining each QDoc, both requests and responses, are named -.xsd, where is the value of the QDoc version attribute. See version. The Response component is appended on response documents only.Versioning for 1.0 Schemas
For all QAD products, it is expected that XML schemas will be required for each reusable data type, such as SalesOrderType or PurchaseOrderLineType, as well as for the QDocs themselves. Because the definitions of the data types will change over time, the XML schema files of the data types are versioned, with different versions of the same data type coexisting in different XML schema files. In fact, it is anticipated that most QDoc version changes will be driven by changes in the underlying data types. The XML schema defining each version of a single QDoc, therefore, includes the XML schema files for the corresponding versions of its component data types. See version. To allow the data type schemas to be referenced by version, each XML schema file defining a data type is named -.xsd, where is assigned in exactly the same manner as for the QDocs.As a general rule, whenever any common data type is revised and obtains a new version, all the QDocs and/or data types containing the revised type must also obtain a new version. This practice is exactly analogous to the propagation of engineering revisions from component item numbers through parent assemblies all the way up to the end product in an engineering or manufacturing bill of material. When a component part has its version incremented, so do all its parent items.Example: A maintainSalesOrder version eB_1 QDoc might contain version eB_1 of the two data types SalesOrderType and SalesOrderLineType. If fields specific to eB2 are added to SalesOrderLineType that affect the QDoc, a version eB2_1 of SalesOrderLineType will be created in XML schema file SalesOrderLineType-eB2_1.xsd. This new file will then be included in the new QDoc XML schema file maintainSalesOrder-eB2_1.xsd.
Moreover, if a QDoc request schema is revised resulting in a new version, a new version of the matching QDoc response schema is also created whether or not it has actually been changed, and vice versa. Thus, any QDoc response always has the same version as its corresponding QDoc request.