Digital Assets

To create or use digital assets its important to understand the following terms

  • Collection

  • Schema

  • Template

  • Asset

Collection

A collection is basically a group, it is used to bring related assets under the same umbrella

While creating a collection its necessary either to create a new collection or to choose from the existing one first

For example, US Polo deals in various categories like clothing, footwear, watches etc so they have created three different collections US Polo Garment, US Polo Footwear, US Polo Watches

Once a collection is created backend assigns a unique id to that collection which is known as collectionId which will be later used in various APIs

Schema

Once the collection is decided next step is to choose or create a schema.

Schema basically represents the skeleton of various different types of asset categories under one umbrella.

For example, in the US Polo Garments collection we can have multiple schemas like shirts, t-shirts, trousers, skirts, jackets etc.

Each schema can have some attributes like a shirt schema can have attributes like, size, colour, sleeves, price etc.

Schema has two types of attributes mutable and immutable, mutable attributes can be changed later but immutable attributes can not change once decided.

Once a schema is added backend assigns a unique id known as schemaId which will be later used in various APIs

Templates

As we mentioned schema is a skeleton so one can put various skins over a skeleton and can create multiple entities.

For example, in the above shirts schema, we have attributes like colour, size, and sleeves so if we give them values like colour = red, size = XL and sleeves = full, it means we created a template of shirt schema type.

Once a template is created backend assigns a unique id known as templateId which will be later used in various APIs

Asset

Assets are basically the actually NFT

They are various copies of one template

Once an asset is created backend assigns a unique id known as cardId which will be later used in various APIs

Last updated