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

[veraPDF-users] validation rule 6.8-4
by Pablo Rodriguez 27 Mar '18

27 Mar '18

Dear list, I have a PDF/A-3a file which veraPDF complains that it violates rule 6.8-4 (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…). I’m afraid there is no text in the wiki for that rule. Would it be possible that this text could be added? Many thanks for your help, Pablo -- http://www.ousia.tk

2 1

[veraPDF-users] document breaking rule 6.4.3-1
by Pablo Rodriguez 21 Mar '18

21 Mar '18

Dear list, I attach a PDF/A-3 document that veraPDF-1.15.1 detects as breaking the rule 6.4.3-1. The extended information shows the following (edited for legibility): PDSignature doesByteRangeCoverEntireDocument == true root/document[0]/AcroForm[0]/formFields[0](7 0 obj PDSignatureField)/V[0](1 0 obj PDSignature) Does the info above mean that the object 7 in the PDF document isn’t included in the signature byte range? Many thanks for your help, Pablo -- http://www.ousia.tk

3 2

[veraPDF-users] plugin deployment
by Jochen Staerk 14 Feb '18

14 Feb '18

Hi, I just release a new preview of my planned VeraPDF plugin (on https://github.com/ZUGFeRD/ZUV/releases/tag/v0.4.1) and unfortunately in the past months a) the need for ph-schematron has been confirmed and b) I could not solve the deployment issues. It turned out I do need ph-schematron, which in turn references saxon, for for performance issues: we're talking about 11 seconds (ZUGFeRD 1) respectively 4 seconds run time per ZUGFeRD file with when checking with XSLT2 (i.e. ph-schematron and saxon2) while it takes 11 *minutes* for a check without, i.e. with java's XSLT1. And so far I could not even produce a XSLT1 for the ZF2 (more precisely UN/CEFACT SCRDM CII 16B EN 16931) schematron. Despite something like java -jar ZUV-0.4.1-SNAPSHOT.jar -f <any ZUGFeRD PDF file like from http://www.mustangproject.org/MustangGnuaccountingBeispielRE-20170509_505.p…> works, if one tries to use the (shaded) ZUV-0.4.1-SNAPSHOT.jar as VeraPDF plugin there will be exceptions like Feb 12, 2018 10:36:31 AM org.verapdf.processor.ProcessorImpl extractFeatures WARNUNG: Exception caught when extracting features of item java.lang.NoClassDefFoundError: org/junit/rules/ExternalResource Does anybody have an idea how this could be solved? I e.g. tried a shaded jar with relocations but that did not work because saxon had to be be refered by it's original name which AFAIK is taken by VeraPDF internal usage. My only remaining straw would be turning the thing around and attempting to embed VeraPDF in the ZUGFeRD validator instead of embedding the ZUGFeRD validator in VeraPDF as a plugin. thanks a lot and kind regards, Jochen Mustangproject.org Chief ZUGFeRD amatuer

2 2

[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

[veraPDF-users] Rule 6.4.3-1
by Pablo Rodriguez 18 Dec '17

18 Dec '17

Dear list, I have a ditally signed PDF/A-3 document, which verapdf-1.9.84 complains about violation of Rule 6.4.3-1. I’m checking a tool for signing PDF documents. And I don’t know whether a part of the PDF document is missing or that it included the signature data themselves. Is there any way that I have to check the Rule 6.4.3-1 for any PDF document (even if not a PDF/A document)? Many thanks for your help, Pablo -- http://www.ousia.tk

2 3

[Users] Rule 6.2.11.4-1
by Pablo Rodriguez 07 Dec '17

07 Dec '17

Dear list, after installing latest devel release (from 1.9.48 to 1.9.89), I have found that a PDF/A-3a file with a digital signature that uses the standard Courier font isn’t embedded. This seems to violate Rule 6.2.11.4-1. Sorry for the stupid question, but does Rule 6.2.11.4-1 apply to the Adobe standard fonts? Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

[Users] on the list identification
by Pablo Rodriguez 06 Dec '17

06 Dec '17

Dear list administrators, would it be possible that the list uses [verapdf-users] instead of just [users] to mark the list messages? This makes identification of messages from the list more easily identifiable in a first look. Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

[Users] Make and validate PDF/A-2A based on Word document
by Stijn De Groof 06 Dec '17

06 Dec '17

Dear users of veraPDF, We are figuring out how to make good, future-proof PDF's based on our day-to-day documents, which are mostly Word documents (DOC and DOCX). For the moment, we are using Word 2016 for Windows. Here, you can choose to save as a PDF/A (save as PDF > options > Conform with PDF/A). When I validate the resulting PDF using veraPDF with PDF/A flavor = auto-detect, it passes (hooray for Microsoft). Looking at the validation report, I see that it gets validated as a PDF/A-3A. This is where it gets interesting. The test document was a simple text document - like most of the documents we create, maybe supplemented with some images. So, I would like to make my document in conformance with PDF/A-2A, as there should not be any embedded file in this simple PDF. In Word, there is no option to make your document in conformance with specific flavors. When I validate the document with veraPDF with flavor PDF/A-2A, I only get 1 error: Rule Status Specification: ISO 19005-2:2011, Clause: 6.6.4, Test number: 2<https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-an…> The value of pdfaid:part shall be the part number of ISO 19005 to which the file conforms. Failed 1 occurrences Show<file:///C:/Users/degroofs/AppData/Local/Temp/veraPDF-tempHTMLReport4783092570292827590.html> So, I guess this means that my document says it isn't a PDF/A-2A, but a PDF/A-3A instead. So, this seems to be a metadata issue. My main question: can I safely ignore this message or change the metadata of my document to make it in conformance with PDF/A-2A? I also went a step further to test this: I opened the PDF document in Notepad++ and I think I found the metadata part in question (using the veraPDF wiki as a guideline). There is this RDF part almost at the bottom that goes like this: <pdfaid:part>3</pdfaid:part><pdfaid:conformance>A</pdfaid:conformance> If you change the 3 in a 2 and save it, the document validates as a PDF/A-2A!!! So mainly 2 questions: 1. Is this safe? 2. Is there a less dirty way to change the flavor of my PDF document in the metadata? Thanks for any help. You can find the files I used and the test results in attachment Kind regards, Stijn De Groof Koninklijk Instituut voor het Kunstpatrimonium (KIK-IRPA) Jubelpark 1, 1000 Brussel, T: +32 2 73 96 779

2 2

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

users