You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having problem with the PDF MediaManagement metadata validation. While I'm putting the document with the Version filled
the PDF/A verifier (https://demo.verapdf.org/) marks it as invalid XMP composition. If all the other fields besides version are set, then there is no problem, so it looks like a problem with serialization of the Versions or ResourceEvent.
While I checked and compared the content of the XMP metadata I've found out that the structures differs compared to some example on the Adobe.
This is a bag of versions created by go-xmp:
<rdf:Bag>
<rdf:listVer:comments="Optimize document to PDF/A standard"stVer:modifyDate="2021-12-08T13:50:51+01:00"stVer:version="1"rdf:parseType="Resource">
<stVer:eventstEvt:action="formatted"stEvt:instanceID="7a023287-49a7-4bf9-b809-4f99c10e0b67"stEvt:parameters="Optimized to PDF/A"stEvt:softwareAgent="Custom Software agent"stEvt:when="2021-12-08T13:50:51+01:00"></stVer:event>
</rdf:li>
</rdf:Bag>
I'm having problem with the PDF MediaManagement metadata validation. While I'm putting the document with the Version filled
the PDF/A verifier (https://demo.verapdf.org/) marks it as invalid XMP composition. If all the other fields besides version are set, then there is no problem, so it looks like a problem with serialization of the Versions or ResourceEvent.
While I checked and compared the content of the XMP metadata I've found out that the structures differs compared to some example on the Adobe.
This is a bag of versions created by go-xmp:
Comparing to some Adobe forum content: (https://community.adobe.com/t5/photoshop-ecosystem-discussions/exif-history/td-p/9931177)
Looks like a ResourceEvent is not set as attributes but separate fields.
Do you know how it could be solved?
If needed I can help in contribution.
The text was updated successfully, but these errors were encountered: