-
Notifications
You must be signed in to change notification settings - Fork 13
Description
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:li stVer:comments="Optimize document to PDF/A standard" stVer:modifyDate="2021-12-08T13:50:51+01:00" stVer:version="1" rdf:parseType="Resource">
<stVer:event stEvt: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>Comparing to some Adobe forum content: (https://community.adobe.com/t5/photoshop-ecosystem-discussions/exif-history/td-p/9931177)
<rdf:Seq>
<rdf:li rdf:parseType="Resource">
<stEvt:action>saved</stEvt:action>
<stEvt:instanceID>xmp.iid:D8D91F3EE568E811852FBF74E8439D24</stEvt:instanceID>
<stEvt:when>2018-06-05T18:24:03+01:00</stEvt:when>
<stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
<stEvt:changed>/</stEvt:changed>
</rdf:li>
</rdf:Seq>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.