Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abstract use of instance/document IDs and provenance for ingredient use #253

Open
brogdonm opened this issue May 22, 2023 · 1 comment
Open
Assignees

Comments

@brogdonm
Copy link
Contributor

Currently, the SDK relies on assets to support XMP to properly be an ingredient. Since not all assets support XMP, would be beneficial to abstract this behavior, to allow for:

  • Optional method for getting a new ID to use for instance/document ID

    This would allow an asset to provide a customized ID instead of one with xmp:*

  • Setting an instance/document ID when signing an asset the first time
  • Getting an instance/document ID from an asset
  • Getting the provenance URI of a remote manifest

The ingredient.rs mod would be able to utilize these new methods to build out the ingredient information and would appropriately support remote manifests.

@gpeacock gpeacock self-assigned this Jul 13, 2023
@gpeacock
Copy link
Collaborator

This is a great idea and on my backlog of things to do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants