ABPSC — Resolve double meaning of "Ancillary"

There is a conceptual confusion about "Ancillary":

(a) The report generates an “ancillary archive” which contains all the attachment stuff from the JIRA process.

(b) The Taskforce Chair is required to provide Maintenance Material, which are SVG images, Models, Document Sources, etc., and that is also called an “ancillary archive”

The report administration page apparently does not understand this distinction. Also, to resolve this confusion and double-usage of “ancillary”, I strongly recommend the introduction of category “Maintenance”, reserved for specification maintenance material, replacing that usage of “ancillary” and be as private as all the ancillary files before.

In addition, Specification Maintenance Archives must have the Version Stamp in their file name (or otherwise associated with the file), so that the particular maintenance archive can be unambiguously associated with the corresponding specification version. Since at least the model inside the maintenance archive is directly associated with machine readable files, the Version Stamp is preferred over the Specification Version.