You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
User does not indicate previous version: A new ISCC-ID:B is minted. (A & B can probably be matched)
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.
The text was updated successfully, but these errors were encountered:
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:
Options:
previous
version: A new ISCC-ID:B is minted. (A & B can probably be matched)previous
version: ISCC-ID:A will be updated to ISCC-CODE:BNotes:
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.The text was updated successfully, but these errors were encountered: