Url needs semantic information

[ericEnjoy]

OriginByte protocol supports url domain for collection and nft object currently, which works fine for collection and nft launching, but it confuse the client how to read and display the url. NFT's url is used in three different ways to show content as I know.

1. metadata url (most are external ERC721 Metadata JSON)
2. image url
3. animation url

So, if url domain contains some semantic infos will be helpful for client to read and show off.

[Suficio]

Thanks for the suggestion!

Could you elaborate as to why the file protocol and MIME type returned in the URL response does not provide sufficient semantic info for these cases?

How would you propose providing this semantic info for the client to read?

[ericEnjoy]

MIME type is not easy for client to read and use, client need the http response to distinguish whether the resource is json, image or video etc. If nft protocol contains semantic info, client will know what type of resource is before fetch the url.
File protocol is a good solution but not mandatory for users, so it still need a semantic info in contract level.

One simple way I can think of is make Url domain with semantic info, such as UrlDomain -> (MetadataUrlDomain, ImageUrlDomain, AnimationUrlDomain). In this way, client will know the resource's type info when get the NFT not after fetch the url.