One for the #reproducibility nerds

Is there an accepted standard (or just some good examples) of how to include provenance metadata within computationally produced images

My specific use case is graphs generated by plotly (python) saved as png where I'd like to record some things like date, software version, data version in the image metadata

There are exif elements for date and "software" but is there a better solution than just shoving info in the description and/or title field? Something that can survive passage through a presentation an added bonus!

(And yes, I do want this in the image metadata, not as a separate file, I'll use the same info to write out a separate manifest)

@cameronneylon Maybe
https://github.com/adobe/XMP-Toolkit-SDK/blob/main/docs/XMPSpecificationPart2.pdf#G4.1133230 suggests stEvt:action of created, stEvt:when of the date of creation, and stEvt:softwareAgent with the software itself which I suppose would include its version.

There are also (from https://help.accusoft.com/ImageGear/v26.3/iptc-metadata-structure.html ) IPTC fields

62 "DigitalCreationDate" STRING 8
63 "DigitalCreationTime" STRING 11
65 "OriginatingProgram" STRING 32
70 "ProgramVersion" STRING 10

Otherwise, maybe https://schema.org/isBasedOn with a URL to the software and data basis for creation?

XMP-Toolkit-SDK/docs/XMPSpecificationPart2.pdf at main · adobe/XMP-Toolkit-SDK

The XMP Toolkit allows you to integrate XMP functionality into your product or solution - adobe/XMP-Toolkit-SDK

GitHub
@datum @cameronneylon XMP is where my mind went as well.