NFT Metadata structure identification

[bigcjat]

I would like to propose a simple standard to NFT metadata on the XRPL. As it's clear NFTs will not use a common standard, I believe we should at very minimum identify the structure in the meta itself.

This way, projects can feel free to use any existing format, or create their own. As long as the format is identified, applications using this metadata can call on the correct function to map the data to their preferred structure. This is a function that can also be shared with the community by either the project introducing it, or by an application that has adapted to it.

An example of an ERC721 structure
{ "title": "Asset Metadata", "type": "object", "schema":"erc721", "properties": { "name": { "type": "string", "description": "Identifies the asset to which this NFT represents" }, "description": { "type": "string", "description": "Describes the asset to which this NFT represents" }, "image": { "type": "string", "description": "A URI pointing to a resource with mime type image/* representing the asset to which this NFT represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive." } } }

The only thing added to the above example (taken from https://eips.ethereum.org/EIPS/eip-721) is the structure being identified "schema":"erc721", We also see this in XLS24d as schema.

Identifying the structure in the meta itself removed the need to attempt to detect the subtle differences before mapping the data for your application. It will increase the speed at which new structures can be adapted to, and rely less on a fallback detection which takes up resources and may produce errors.