Closed arational closed 10 months ago
According ISO19005-3(Table E.1) the AFRelationship key should have type Name, but veraPDF allowed this key to be a name or a string. This issue was fixed in veraPDF1.24.
Thanks for the quick reply! I don't have the PDF/A-3 specification by hand right now. What do you mean by type Name? How this line with /AFRelationship(Data)
(see above) should look like to conform to this rule?
Alright, I got it now, it should be this way: /AFRelationship/Data
.
Thanks a lot for your help! I'll close this PR then, as the error is on our side.
Validating the attached PDF with Version 1.22 doesn't report any violations. However, validating the same PDF file with Version 1.24 complains about following rule:
https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-68-3
Looking into the PDF-Stream and the relevant line, the
AFRelationship
entry is present in the dictionary and sets it's value toData
.simple.pdf