Hi all Any advice? Thanks and kind regards, Tony
Von: Tony Schaller Gesendet: Montag, 30. Oktober 2017 15:44 An: 'users@lists.verapdf.org' users@lists.verapdf.org Betreff: Unexpected validation rules in the veraPDF validation report
Hi
We have integrated veraPDF validation-model 1.8.1 from the maven repo (https://mvnrepository.com/artifact/org.verapdf/validation-model) into the eHealth Connector Open Source project (see https://sourceforge.net/projects/ehealthconnector/). See https://sourceforge.net/p/ehealthconnector/wiki/CDA%20Validation/ for more information.
The eHealth Connector API is converted by IKVM.net into a .Net DLL and is therefore available on both platforms
While validating PDFs I'm confused about the veraPDF behavior: Using the Java Demo of the eHealth Connector, the report shows exactly the same as your validation tools (http://software.verapdf.org/releases/1.8/verapdf-greenfield-1.8.1-installer....). But using the .Net Demo I alwas get two additional issues in the report: Rule 1 - Specification: ISO 19005-1:2005, Clause: 6.2.2, Test number: 1 Error: A PDF/A-1 OutputIntent is an OutputIntent dictionary, as defined by PDF Reference 9.10.4, that is included in the file's OutputIntents array and has GTS_PDFA1 as the value of its S key and a valid ICC profile stream as the value its DestOutputProfile key See also: https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-1-rule... 1 Occurrence(s): - root/document[0]/outputIntents[0]/destProfile[0] Rule 2 - Specification: ISO 19005-1:2005, Clause: 6.2.3, Test number: 5 Error: All ICCBased colour spaces shall be embedded as ICC profile streams as described in PDF Reference 4.5. The number of color components in the color space described by the ICC profile data must match the number of components actually in the ICC profile. As of PDF 1.4, N must be 1, 3, or 4 See also: https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-1-rule... 1 Occurrence(s): - root/document[0]/outputIntents[0]/destProfile[0]
I have investigate a lot in finding the issue within the eHealth Connector but I'm sure, that the PDF that is handover to veraPDF is identical on both platforms. Therefore I'm kind of helpless now. And while I do not bring in-depth knowledge with your validation-model I'm currently lost. In the meantime I decided to suppress these two messages (see https://sourceforge.net/p/ehealthconnector/code/HEAD/tree/trunk/ehealthconne... ) but I'm sure that this is not what we should do.
Any advice is heavily appreciated.
Thanks and kind regards, Tony