users December 2017

users@lists.openpreservation.org

3 participants
5 discussions

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

users December 2017