The collection is a Map( vec {(Text; Value)}, so you should be able to put whatever you want in and it can be returned with icrc7_collection_metadata. The other functions you mentioned are there for convenience, but the full metadata is returned by icrc7_collection_metadata. See:
|ICRC|Title|Author|Discussions|Status|Type|Category|Created|
|:----:|:----:|:----:|:----:|:----:|:----:|:----:|:----:|
|7|Minimal Non-Fungible Token (NFT) Standard|Ben Zhai (@benjizhai), Austin Fatheree (@skilesare), Dieter Sommer (@dietersommer), Thomas (@sea-snake), Moritz Fuller (@letmejustputthishere), Matthew Harmon|https://github.com/dfinity/ICRC/issues/7|Draft|Standards Track||2023-01-31|
# ICRC-7: Minimal Non-Fungible Token (NFT) Standard
ICRC-7 is the minimal standard for the implementation of Non-Fungible Tokens (NFTs) on the [Internet Computer](https://internetcomputer.org).
A token ledger implementation following this standard hosts an *NFT collection* (*collection*), which is a set of NFTs.
ICRC-7 does not handle approval-related operations such as `approve` and `transfer_from` itself. Those operations are specified by ICRC-30 which extends ICRC-7 with approval semantics.
## Data Representation
This section specifies the core principles of data representation used in this standard.
### Accounts
show original
1 Like