Example of Assets with Schemas
Here we will use party bears (collectionId 303204 on Porcini) as an example to create schemas, and then equip the party bear dynamically through the schema.
https://ar-docs.futureverse.dev/schema/
https://ar-docs.futureverse.dev/collection/
https://ar-docs.futureverse.dev/manage-assets/QXNzZXQ6NzY3Mjpyb290OjMwMzIwNDoyMzI=
https://ar-docs.futureverse.dev/manage-assets/QXNzZXQ6NzY3Mjpyb290OjMwMzIwNDoyMzI=
Schemas need to be created to describe asset relationships. Asset Register service provides a Schema Management system to get you going.
Creating schemas is a two-step process. First, you must create the namespace which a schema will live under. A namespace contains a set of schemas that describe something in the same domain. For example the http://schema.futureverse.com/tnl
the namespace will contain the Boxer, Gloves
, HairStyle
and HairDye
schemas for The Next Legends.
We are creating a front-end experience to make this a lot easier instead of going through and making API calls.
A namespace can only be created if the namespace owner has been whitelisted under a domain.
This functionality is in development. In the meantime, please ask the Asset Register team for access to a namespace.
A valid SIWE token with a signature must be set as the Authorisation Header.
When you create a new schema under a pre-existing schema entity it will create a new version.
To create a schema it is the same as above. Ensure that the version is incremented by 1 otherwise, it will fail.
An asset must be registered to a schema in order to generate the Asset Tree.
Currently, anyone can make the call to register a collection with a schema. Eventually, this will be locked down to the owner of the on-chain collection based on the owner of the NFT contract.
Only the off-chain asset creator can register a schema to the asset.
Same as Registering an on-chain asset with a schema.