A PDF/A conversion or validation XML report is provided in various situations:
•In the Web portal
If a PDF/A conversion could not be completed successfully, for example
•When calling the "Pdfa" web service
In the web service’s analysis mode (analyze), for example
The XML report has three sections under the "<report>" main node:
<analysis> = All problems or errors found before the attempt to convert the document to PDF/A format was made.
<post-analysis> = All problems found that are still present after the conversion to PDF/A format is performed, i.e., problems that could not be corrected.
<result> = Error code for the conversion performed (0 =successful conversion)
Error and fixes
The result of the PDF/A conversion or validation operation will be found in the "<result>" node, under "<error>". If there is a “0” there, then the operation was successful.
If there is a negative number here, then an error occurred. This error number will sometimes be supplemented with an additional error number in the "<sub-error>" line if this additional error number is also negative.
For details on why a conversion or validation (analysis mode: analyze) was unsuccessful, you can consult the "<analysis>" and "<post-analysis>" sections.
In a PDF/A operation, there are always two analysis steps performed:
1.An analysis of the problems in the PDF document ("<analysis>") before conversion
2.An analysis of the problems in the converted PDF document ("<post-analysis>")
If there are errors in "<post-analysis>", this means that the PDF file could not be converted or that the file is not valid in terms of the PDF/A standard being checked.
<analysis warning="61" info="0" error="4">
The "warning," "info," and "error" attributes in the "<analysis>" node (all the following information applies to "<post-analysis>" as well) will provide the total number of problems. The "<detail>" node, which may be found more than once, will list the individual problems. Further attributes are contained there:
•type = severity of the problem (error, warning, information)
•page = The page in the document on which the error occurred (if the page is "0", then it applies to a global PDF object)
•object = ID of the internal PDF object which has caused the problem
•count = The number of times the error is repeated in the entire document
•code = Internal PDF/A-converter error code
The text in the "<detail>" node will provide a text description of the error.
Analysis mode for PDF/A validation
In addition, there is also the option of calling the "Pdfa" web service in analysis mode (analyze). In this mode, the PDF document is not converted. Instead, it is only analyzed. The result, instead of a PDF document, is an XML report. The analysis mode is used, for example, when the "Pdfa" web service is used on a gateway that needs to make sure that only valid PDF/A documents are accepted (e.g., for an archive).