Feature request on verification result.

[Reissner]

For instance if verifying with

verapdf xxx.pdf --format html xxx.html

the result contains the full path of xxx.pdf.
I think, this unveils the environment which is not secure and it does not savely relate the 'certificate' xxx.html to the according document, because you can move that and can place another one at the same path.

Better would be to include the trailer id into the xxx.html, likewise for xxx.json.
I create pdf from latex.
That way even the compilation run is fixed.
Then it is perfectly reasonable not to give the full path, just the filename.

[bdoubrov]

@Reissner I see multiple requests here:

• removing full path and leaving only a file name: this indeed is a great suggestion, and we'll include it into our dev backlog. The only question here is what is the expected behavior in case of the batch job? Probably, we'd want to keep the relative path, not just the file name.
• adding trailer IDs is a also a good suggestion. We would need them in JSON, XML and HTML reports

[Reissner]

Ah, you mean the path from the folder where invoked and where the pdf resides? yes, you are right, this is better.
Yes trailer id.. avoids cheating and erroneous confirmation: Assume you created a PDF, then verified and created another one at the same place without verifying, maybe not passing the tests.
Currently, this is undetected.

Yes, it is for all output formats, except maybe text... well even for text it is nice, why not.