OptionalassertionsA list of assertions
Optionalclaim_Claim Generator Info is always required with an entry
Optionalclaim_The version of the claim. Defaults to 2.
OptionalformatThe format of the source file as a MIME type.
Optionalhash_Hash algorithm used for asset hashing (DataHash, BmffHash) and assertion hashing
in the claim. Defaults to "sha256" when not set.
Valid values: "sha256", "sha384", "sha512".
This sets the claim-level alg field and is the default used by
[Builder::update_hash_from_stream]. It can be overridden on individual
hard binding assertions (e.g. a pre-constructed DataHash) by setting
the assertion's own alg field before adding it to the builder.
Named hash_alg (rather than alg) to avoid collision with the signer's
signature algorithm, which uses the same key in some combined JSON configurations.
OptionalingredientsA List of ingredients
Optionalinstance_Instance ID from xmpMM:InstanceID in XMP metadata.
OptionallabelAllows you to pre-define the manifest label, which must be unique. Not intended for general use. If not set, it will be assigned automatically.
OptionalmetadataOptional manifest metadata. This will be deprecated in the future; not recommended to use.
OptionalredactionsA list of redactions - URIs to redacted assertions.
OptionalthumbnailAn optional ResourceRef to a thumbnail image that represents the asset that was signed. Must be available when the manifest is signed.
OptionaltitleA human-readable title, generally source filename.
OptionalvendorOptional prefix added to the generated Manifest Label This is typically a reverse domain name.
Use a ManifestDefinition to define a manifest and to build a
ManifestStore. A manifest is a collection of ingredients and assertions used to define a claim that can be signed and embedded into a file.