From 3f656a7e12fa8aafb303698223d2ed7a0f15ade0 Mon Sep 17 00:00:00 2001 From: Shahan Khatchadourian Date: Tue, 25 May 2021 07:50:35 -0400 Subject: [PATCH 1/2] Added clarity to data field description --- docs/architecture/adr-043-nft-module.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/architecture/adr-043-nft-module.md b/docs/architecture/adr-043-nft-module.md index 8f1176bc942d..f3f2bf38fbf6 100644 --- a/docs/architecture/adr-043-nft-module.md +++ b/docs/architecture/adr-043-nft-module.md @@ -63,9 +63,14 @@ The NFT conforms to the following specifications: ``` owner (address) --> []string ``` - * Data: This mutable field allows for attaching pertinent metadata to the NFT, e.g., to record special parameter change upon transferring or criteria being met. - The data field is used to maintain special information, such as name and URI. Currently, there is no convention for the data placed into this field, - however, best practices recommend defining clear specifications that apply to each specific NFT type. + * Data: This mutable field allows attaching special information to the NFT, for example: + * metadata such as title of the work and URI + * immutable data and parameters (such actual NFT data, hash or seed for generators), + * mutable data and parameters that change when transferring or when certain criteria are met (such as provenance) + + This ADR doesn't specify values that this field can take; however, best practices recommend upper-level NFT modules clearly specify its contents. + Although the value of this field doesn't provide additional context required to manage NFT records, which means that the field can technically be removed from the specification, + the field's existence allows basic informational/UI functionality. The logic for transferring the ownership of an NFT to another address (no coins involved) should also be defined in this module ```go From 7feabee38338d0ecb3625d2d185030a843077650 Mon Sep 17 00:00:00 2001 From: Shahan Khatchadourian Date: Tue, 25 May 2021 08:39:25 -0700 Subject: [PATCH 2/2] Update docs/architecture/adr-043-nft-module.md Co-authored-by: Aleksandr Bezobchuk --- docs/architecture/adr-043-nft-module.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/adr-043-nft-module.md b/docs/architecture/adr-043-nft-module.md index f3f2bf38fbf6..108b255d514c 100644 --- a/docs/architecture/adr-043-nft-module.md +++ b/docs/architecture/adr-043-nft-module.md @@ -65,7 +65,7 @@ The NFT conforms to the following specifications: ``` * Data: This mutable field allows attaching special information to the NFT, for example: * metadata such as title of the work and URI - * immutable data and parameters (such actual NFT data, hash or seed for generators), + * immutable data and parameters (such actual NFT data, hash or seed for generators) * mutable data and parameters that change when transferring or when certain criteria are met (such as provenance) This ADR doesn't specify values that this field can take; however, best practices recommend upper-level NFT modules clearly specify its contents.