TIP-27 IOTA NFT standards #65
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
|
|
||
| { | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "$id": "https://github.com/iotaledger/tips/main/tips/TIP-0027/irc27.schema.json", | ||
| "title": "IRC27 IOTA NFT Metadata Schema", | ||
| "description": "A JSON schema for validating IRC27 compliant NFT metadata", | ||
| "type": "object", | ||
| "properties": { | ||
| "standard": { | ||
| "type": "string", | ||
| "description": "identifier for the metadata standard used", | ||
| "pattern": "^IRC27$" | ||
| }, | ||
| "version": { | ||
| "type": "string", | ||
| "description": "version of the metadata standard used", | ||
| "pattern": "^v\\d+.\\d+$" | ||
| }, | ||
| "name": { | ||
| "type": "string", | ||
| "description": "A descriptive name of the token" | ||
| }, | ||
| "description": { | ||
| "type": "string", | ||
| "description": "some information about the NFT project" | ||
| }, | ||
| "type": { | ||
| "type": "string", | ||
| "description": "MIME type of the asset" | ||
| }, | ||
| "uri": { | ||
| "type": "string", | ||
| "description": "URI pointing to the resource where the file with `type` MIME type is hosted" | ||
| }, | ||
| "collectionName": { | ||
| "type": "string", | ||
| "description": "A human readable name for the NFT collection" | ||
| }, | ||
| "royalties": { | ||
| "type": "object", | ||
| "description": "object containing the payout addresses mapped to their percentage share" | ||
| }, | ||
| "issuerName": { | ||
| "type": "string", | ||
| "description": "name of the artist" | ||
| }, | ||
| "attributes": { | ||
|
There was a problem hiding this comment. I would recommend to get inspired from ERC-721 / ERC-1155 metadata standard:
There was a problem hiding this comment. We are heavily inspired by the ER721 standards, camelCase or snake_case are acceptable in word separation as per JSON schema standards. For example the I am sure Merul can comment a little further in regard to the localisations.
There was a problem hiding this comment. I am not sure what you mean by localization here but if you mean glyphs from other languages than that shall be covered by unicode already |
||
| "type": "array", | ||
| "description": "array containing any additional data as objects." | ||
| } | ||
| }, | ||
| "required": [ "standard", "type", "version", "uri", "name" ] | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should consider index here. You might want to define sequence as not all royalties might be paid every time. For example, what happens if the royalty is below dust?