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

Define previous semantics (does it preserves a pre-registered ISCC-ID - declaration related) #15

Open
titusz opened this issue Jan 8, 2022 · 0 comments

Comments

@titusz
Copy link
Member

titusz commented Jan 8, 2022

The previous field allows for linking back to a previous version of a digital asset.
In context with ISCC declarations this would give an opportunity to give an ISCC-ID persistence.

Example:

  • User declares ISCC-CODE:A which creates ISCC-ID:A
  • User updates the digital asset.
  • User redeclares the asset with new ISCC-CODE:B

Options:

  1. User does not indicate previous version: A new ISCC-ID:B is minted. (A & B can probably be matched)
  2. User does provide the ISCC-ID of previous version: ISCC-ID:A will be updated to ISCC-CODE:B

Notes:

With option 1 ISCC-ID:A will persistently and immutably refer to the snapshotted version of the digital asset. Other versions of the digital asset may be match-able via similarity of their linked ISCC-CODEs.

Option 2 would allow ISCC-ID:A to persistently refer to the latest version of a given asset and provide a user-controlled immutable history of its updates. This would be of use if a publicly circulated ISCC-ID should always link to the latest version of a given asset.

For option 2 to work the link to the previous version must be part of the on-chain declaration message to support stable minting semantics.

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

1 participant