If you’d like a preview of a more explicit static/dynamic nft metadata standards, see NFT Working Group - Next Steps - ICRC-8, ICRC-56, ICRC-59, ICRC-60 for ICRC-59 and ICRC-60. These desperately need to be updated and streamlined, but they are generally in the right direction.
The idea here is that for WALLETs you would always want the ICRC-97 entry as it will be the most direct to implement. For other kinds of applications you would ADD the ICRC-59 or ICRC-60 entry to augment it for applications that want to handle processing static or dynamic data on-chain by other canisters. Similar to the example given with com.mygame.namespace above but with ICRC-59 or 60 fields.
I’d expect 59 to end up with something along the lines of “icrc59:isStatic”, #Text(“true”) to flag that the data in the icrc97 will never change.