Feature Description

There are various ideas about how to improve Schemas. Let's discuss and find a way forward on it.

• Schemas have three implied and real pieces
  • Protocol namespace (dsnp and frequency on Mainnet)
  • Schema (dsnp.update for example)
  • Schema Version (dsnp.update v1 and v2 for example)
• Delegations are at the Schema Version level, the other levels are merely structure
• Protocol authors cannot upgrade independent of new schema version and asking each user to approve

Concerns/Tradeoffs

• How can users be protected from bad schema upgrades?
• How can users not be bothered by schema upgrades that have only structural differences?
• How can the delegation model be improved/changed to handle the multi-layer schema structure (specifically different versions)?
• How can the interaction model with schemas be unified and simplified (even at the expense of complexity in schema creation)?
• How can the Ethereum integration work align with these changes?

Searched for Related Issues

• I have done a search for related issues and either found none, or noted them