Formatting json data stored in text records?

[0xc0de4c0ffee]

This is related to #1 headers records type and ENS forum discussion about "showcase" text records.

We're dumping big json string on text records off-chain, so IF we should go one step ahead and prefix it with proper data:[<mediatype>][;base64],<data>? RFC2397

data:application/json,[
    "eip155:<chain_id>/<NFT_Type>:<contract_addr_orENS>/<NFT_ID>",
    "eip155:1/erc1155:0xb32979486938aa9694bfc898f35dbed459f44424/10063",
    "eip155:1/erc721:bensyc.eth/666"
]

wrapping that json data inside .json {data: "data:text/json..."}

let _data = "data:application/json,..." // actual data
let showcase_json = {data: <abi.encode(_data)>} // "data:" here is CCIP format record
// signed version
let showcase_json2 = {data: <__callback.selector + abi.encode(abi.encode(_data), signature, signer)>}

This is more similar to avatar records resolved from ERC721/1155 URIs are compatible with data:... formatted NFT records.

So we should think about different app/service specific data/types dumped on text records.
& back to IPLD topic on ENS forum it'd be nice to have direct data:uri support on contenthash so we could run html/svg generators on-chain or other generators types to read on-chain data and output data:application/json,{..} linked with sub-domain mappers example, <0xaddr>.balanceof.dai.xtoken.eth.

One more record that we've to speed up is "MARKET" record for owners to setup a signed buy/sell orders..
e.g, pay x $ETH to market contract with this signature to buy this domain.eth.
it's similar to selling on nft markets but the signed data is stored in domain's text record for open markets to read/display.

[0xc0de4c0ffee]

https://discuss.ens.domains/t/nft-showcase-ens-record-and-record-standardization/16894/33

[0xc0de4c0ffee]

serenae : Yeah it’s probably a good idea to make it a URI, so you can use a direct data: URI if you need to. Theoretically it could be any other scheme too, like a gateway server.

https://discuss.ens.domains/t/draft-ensip-off-chain-name-meta-resolution/17019/6

If json/any content is dumped in text records it's good idea to prefix as data URI. except for plaintext.

• data:application/json,... for json text records
• data:text/html,... for html text records
  ...