November 2017 - users@lists.openpreservation.org - Open Preservation Foundation mailing lists.

[Users] veraPDF and thread-safeness?
by Tony Schaller 09 Feb '18

09 Feb '18

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 supports multithreading, but veraPDF seems not currently to be thread-safe. Is there any plan for a thread-safe veraPDF validation-model? Thanks in advance for any response. Regards, Tony

2 8

[Users] VerPDF build
by Bengt Neiss 15 Nov '17

15 Nov '17

Hi, I am trying to build VeraPDF from based on the instructions in the README.md I am building the software on a RHEL7 server with OpenJDK 1.8.0_151 (and I am aware that the readme says Java 7) and it is the latest release source that are being used. However, when using the "mvn clean install -P clone-test-resources" I get the following warning - " [WARNING] The requested profile "clone-test-resources" could not be activated because it does not exist". Has I missed something or isn't the Readme up-to date? The build ends succesfully but when I try to start by issuing the "java -jar gui/target/gui-1.8.0.jar" I get the message " No main manifest attribute, in gui/target/gui-1.8.0.jar". Is this due to trying to use Java 8 or is it related to something else? Thanks in advance, Bengt Neiss

2 1

[Users] Unexpected validation rules in the veraPDF validation report
by Tony Schaller 07 Nov '17

07 Nov '17

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-rul… 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-rul… 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/ehealthconn… ) but I'm sure that this is not what we should do. Any advice is heavily appreciated. Thanks and kind regards, Tony

2 3