Display support some nessesary fields

[ericEnjoy]

I've been working on the protocol recently, I found that the standard only allows a few fixed fields for now, like adding name / description / url to the collection etc. I have some questions and I would like to provide more fields for the standard, like social media / website etc, some fields I think are necessary. Can these fields be supported.
I also noticed that there is an RFC for display, and it seems like a good solution to use dynamic object as a container for the fields to increase the flexibility of the fields, when will this solution be implemented?

[kaizu-xyz]

The protocol is made such that individual collections can create their own custom fields and add them to the NFT via calling nft::add_domain. However, we want to actively add domains to our contract directly for the purpose of standardizing the majority of use cases. We will add a domain for social media in our standards in this merge cycle :)

We are also working on our byte cli which will allow creators to create collections and define custom fields to add to the collection. This cli will be available by the end of this week / beginning of next one.

In relation to the implementation of the dynamic fields, we are already using that on our protocol. We are still however designing the mechanism to render complex use cases on the UI such as composable and dynamic NFTs.

[ericEnjoy]

Cool. In our experience, social media is used in most use cases, as is the website fields. We propose to include website as a protocol level supported field, so that creators can have this option.