#verapdf — Public Fediverse posts

As #veraPDF feature reports may be very long, I created a basic XSL file to extract only elements identified by @bitsgalore in his post https://bitsgalore.org/2023/05/25/identification-of-pdf-preservation-risks-with-verapdf-and-jhove.html

Certainly not perfect, but it seems to work...

https://gist.github.com/BertrandCaron/a4e07f2e0c9f1db79cb265d112bc05ab

#digipres

#veraPDF 1.28.2 is out now! This release sees updated dependencies with vulnerability warnings, updates to (PDF/UA-2, WTPDF) and fixed validation of Unicode ✍️🧑‍💻 Read more: https://openpreservation.org/news/verapdf-1-28-2-released/?q=3

As always, HUGE shout to the Dual Lab development team for all their efforts! #digipres

I don't care if #Acrobat thinks, something with an alt-text shouldn't be embedded in somthing else that also has an alt-text. Both #PAC and #VeraPDF are happy with the PDF/UA-1, and so am I... https://publishup.uni-potsdam.de/opus4-ubp/frontdoor/deliver/index/docId/67222/file/pardes30.pdf #TeXLaTeX #accessibility

Sort of a #PDF #doubleTrouble release day at the Open Preservation Foundation today, with new releases of both #veraPDF (which checks conformance to PDF/A and PDF/UA) and the #Arlington PDF Checker (which checks conformance to the Arlington PDF model):

https://openpreservation.org/news/verapdf-and-arlington-1-28-released/

Good stuff!

Hello @Georgia !

I wanted to use the online public demo #veraPDF #Arlington model at https://arlington.verapdf.org/ but it returns a 502 "Bad gateway" error...

🚀 Join @carl today at #iPRES2024 where he demonstrates #veraPDF's #Arlington, an invaluable resource for anyone developing or testing #PDF #DigitalPreservation tools.

📍 De Bijloke - Kraakhuis

Check the release notes here + our thanks go to all contributors, particularly the Dual Lab development team, for their work on this : https://openpreservation.org/news/arlington-pdf-model-checker-released/

Just found out there's now a development prototype of veraPDF-rest, which exposes #VeraPDF's functionality through a REST API:

https://github.com/veraPDF/veraPDF-rest

Will need to try this out, but this definitely looks really useful!

This could also be good for developing performant VeraPDF wrappers in other programming languages, like Python (similar to how Tika-python currently wraps around #Apache #Tika's REST API).

New blog entry: PDF debugging. I show my favourite tools for examining PDF file in case I messed up and get a warning in Adobe Acrobat for example. No more error messages!

https://news.speedata.de/2024/03/14/pdfdebugging/

#pdf #debugging #qpdf #pdfcpu #adobeacrobatpro #verapdf

Hi Kids, wanna validate your PDF files over REST?
https://github.com/veraPDF/veraPDF-rest
Demo here: https://demo.verapdf.org/

#pdfvalidate #veraPDF

ICYMI, I ran some experiments to see if #VeraPDF’s parse status can be used to predict #PDF rendering problems, using an existing dataset of synthetic PDFs as ground truth. I also looked at how this compares against the occurrence of #JHOVE validation errors.

Details in this blog post:

https://www.bitsgalore.org/2023/06/29/verapdf-parse-status-as-a-proxy-for-rendering

New blog post - #VeraPDF parse status as a proxy for #PDF rendering: experiments with the Synthetic PDF Testset:

https://www.bitsgalore.org/2023/06/29/verapdf-parse-status-as-a-proxy-for-rendering

@general

Oh, this looks good - #OpenPreservationFoundation #OPF and the #PDFAssociation have released a first development preview of a #VeraPDF-powered #PDF checker. The software is based on the #Arlington PDF model, and analyses PDF files against the full PDF 2.0 specification:

https://openpreservation.org/news/development-preview-pdf-file-checker-based-on-the-arlington-pdf-model/

Haven't tried it yet, but based on what I'm reading this looks like the future of #PDF validation to me!

Out of curiosity I ran both #JHOVE and #VeraPDF on the "Synthetic #PDF Testset for File Format Validation" by @mickylindlar et al. (link: https://www.radar-service.eu/radar/en/dataset/JtlOdwQquZWDqQdq).

Then did a quick comparison between validation errors as reported by JHOVE, and parse errors and logged warnings by VeraPDF.

Main result so far is that majority of PDFs for which JHOVE reports validation errors, also result in either parser error or warning in VeraPDF. Sneak peek here:

https://github.com/KBNLresearch/pdf-characterisation/blob/main/output/lindlar-tunnat-wilson/jhove-vera-status-errors-warnings.csv

I explored to what extent #VeraPDF and #JHOVE can be used to identify #PDF features that are potential preservation risks. Check out this (massive!) blog post for the full lowdown #wtfPDF:

https://www.bitsgalore.org/2023/05/25/identification-of-pdf-preservation-risks-with-verapdf-and-jhove

Many thanks to Carl Wilson, Boris Doubrov and #OPF #OpenPreservationFoundation for a fantastic update on the latest in #veraPDF this morning/afternoon!

https://openpreservation.org/events/verapdf-to-infinity-beyond-validation/?q=6334

#OPFOAG Thomas Ledoux advocates for a standard #schematron edition tool to enforce institutional policies on #JHOVE, #veraPDF & #jpylyzer outputs.

#OPFOAG Thomas Ledoux advocates for a standard #schematron edition tool to enforce institutional policies on #JHOVE, #veraPDF & #jpylyzer outputs.

@mickylindlar
Carl: "PDF is a huge tree of objects linked one to another." Which makes interpreting errors far from intuitive!

But #veraPDF, and soon #JHOVE, should be able to associate an error to the problematic zone in the PDF.