Currently, if context checking is on, XML validity is done in real time in Arbortext Editor. Another method to validate XML is to manually run the "cc" command (check completeness). One major advantage to running "cc" is that other forms of validation, including Schematron, are run as well ("enhanced completeness check"). Our customer has requested that this run automatically, because their technical writers do not remember to run it manually.

The standard technique to accomplish this is to write custom ACL functions using the "aliases" for File Save, File Close, Application Exit, etc. However, because the SDL LCA Authoring Bridge has fairly complex routines that run on Close and Check-In (and which I believe may also include alias overrides for some of those commands mentioned earlier), it is my feeling that it is extremely risky for us to make any modifications to Authoring Bridge code, or add our own functions to override those Arbortext aliases.

Has anyone implemented something like this? 

We are running LCA 2014 SP3 (i.e. "version 11"). We plan to upgrade to TD14 by the end of the year, in case that would make this easier or less risky.

(I have also opened a support ticket on this just to establish a paper trail, although I suspect this could end up an RFE or PS request in those realms.)

Thanks!