next up previous contents
Next: Conditional Verification Up: User Defined Verification Routines Previous: User Defined Verification Routines   Contents

Error Accounting

Though the exact interface to the fieldspace object, as far as accounting goes, is beyond the scope of this document, there are some general principles that can be discussed here. First of all, user defined checks should only be used if the checks supported directly by the field objects are insufficient. What is defined by MIC, however, is that the user functions must return a true false value in every call to the function.

By accounting, we mean that it is necessary to put fields in error and remove them from that state when appropriate. This should be done carefully and the logic of the functions should be carefully checked to make sure that the accounting is done correctly.

Additionally, MIC is also concerned with whether the MICverify itself is in error or not. Therefore, the function should return a true or false value to indicate that no errors or at least one error was found, respectively. As noted in the MICverify definition, this will control the display of the MIC-HTML error text contained by the MICverify open and close tags.


next up previous contents
Next: Conditional Verification Up: User Defined Verification Routines Previous: User Defined Verification Routines   Contents