That way I can:
- have my detailed Kind 9 Chat message "lexicon"
- document it in a wiki that doesn't need to be merged necessarily (yet still becomes more valuable, the more it is referenced/zapped/replied/accepted in communities/....)
- reference it transparently at the app-level without having to stipulate in each message what spec is being used (which comes with privacy issues etc...)
How would you do lexicons btw, in a way that's backwards compatible? nostr:npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx
Over there the protocol simply mandates both backwards and forwards compatibility. But often times the thing to is to reference another lexicon, or to create a sub schema.
So let's say in a lexicon called:
com.example.post
I have an author field, and for that field I want to reference the profile definition in another lexicon called com.example.user, I pop in:
"author": {"type": "ref", "ref": "com.example.user#/defs/profile"}
And that references:
"profile": {
"type": "object",
"properties": {
"handle": {"type": "string"},
"displayName": {"type": "string", "maxLength": 256},
"avatar": {"type": "string", "format": "uri", "nullable": true}
}
Then it's all just lego blocks and you can worry about them block by block.
But even if you have a breaking change and you come up with a new lexicon for it, all the other apps using the old lexicon will continue to use it, it can't be deleted, so you've not broken anything on their end.
Lo, they think they're messy :winkwithtongue:
