I'm trying to generate valid PDF/A via ConTeXt, but the verapdf validator is reporting an error.
My input document is
\setupinteraction
[title={TITLE},
author={AUTHOR}]
% attempt to generate PDF/A
\setupbackend
[format=pdf/a-3a,
profile={sRGB.icc},
intent=sRGB IEC61966-2.1]
\setupbackend[export=yes]
\setupstructure[state=start,method=auto]
\starttext
\input knuth
\stoptext
Compiling this with context test.mkiv
and testing with verapdf test.pdf
leads to the following validation error:
<validationReport profileName="PDF/A-3A validation profile" statement="PDF file is not compliant with Validation Profile requirements." isCompliant="false">
<details passedRules="130" failedRules="1" passedChecks="1684" failedChecks="1">
<rule specification="ISO 19005-3:2012" clause="6.6.2.3" testNumber="7" status="failed" passedChecks="0" failedChecks="1">
<description>All properties specified in XMP form shall use either the predefined schemas defined in the XMP Specification,
ISO 19005-1 or this part of ISO 19005, or any extension schemas that comply with 6.6.2.3.2.</description>
<object>XMPProperty</object>
<test>(isPredefinedInXMP2005 == true || isDefinedInMainPackage == true || isDefinedInCurrentPackage == true) && isValueTypeCorrect == true</test>
<check status="failed">
<context>root/document[0]/metadata[0](15 0 obj PDMetadata)/XMPPackage[0]/Properties[2](http://purl.org/dc/elements/1.1/ - dc:description)</context>
<errorMessage>An XMP property is either not not pre-defined, is not defined in any extension schema, or has invalid type.</errorMessage>
</check>
</rule>
</details>
</validationReport>
Is there a way to avoid this validation error? I've tried to use a different PDF/A flavour like pdf/a-1a:2005, but that doesn't change anything.
profiles > profile specification 'sRGB IEC61966-2.1' loaded from '/usr/share/texmf/tex/context/colors/icc/context/colorprofiles.xml'
, I guess that's the expected thing? Karl Pettersson helped me to narrow the error down to thedc:description
entry in the metadata: removing it stops veraPDF from complaining. I don't understand the specs well enough, but to me this looks like it might be a problem with veraPDF?