Can we add SpecRevision=<revision level of Content Spec> to the header (under ID=<id>) of Content Specs that are output by the pull --post command? On push --new, if a SpecRevision is detected in the header it should give an error, similar to the one that is given if an ID is present: "SpecRevision attribute is present, and is not allowed when pushing a Content Spec as new" On push --edit, if the SpecRevision does not match the current revision of the Content Spec being edited, then it should fail with: SpecRevision: <revlevel> Current Revision: <revlevel> Revision levels must match to edit.
And what to do if SpecRevision is missing on --edit? Fail with: "SpecRevision" attribute not found in Content Specification.
Added. SpecRevision will automatically be added/updated when pushing in a content specification. The SpecRevision tag must be under the ID and above the Title attributes. Error messages are implemented as described above, except if the revisions don't match. The output from non-matching revision numbers is shown below: ERROR: Invalid Content Specification! Revisions must match to be edited. -> SpecRevision: 12 -> Current Revision: 14