JSON Example
Here is an example of how the Provenance Schema is represented in JSON format. This example illustrates the structure of the manifest_store
, with a sample manifest, actions, and assertions related to the content:
Explanation of the JSON Structure:
manifest_store: This contains the active manifest and a collection of all manifests tied to the content.
active_manifest: This identifier points to the most recent manifest that holds the current state of the content’s provenance.
manifests: The collection of manifests identified by their UUIDs. Each manifest contains metadata like the claim generator, content title, format, instance ID, ingredients, assertions, and signature information.
claim_generator: This shows the tool or system (e.g., Hash Network’s implementation) used to generate the provenance claims.
assertions: These are the key claims related to actions performed on the content, such as creation actions that include the software used (e.g., Stability AI's SDXL model).
signature_info: This section holds cryptographic details, ensuring that the content’s authenticity and integrity are verifiable.
This JSON example showcases a simple but comprehensive structure for managing and verifying the provenance of digital content, in line with the C2PA standards.
Last updated