Current message kinds are for social networking, but if you wanted online stores for example, you'd have to define a new set of message kinds.
Unless you have a k-v storage / graph database. Then you can do nostr.put('npub123/store/items/socks/description', 'Pair of alpaca socks').
And you can change that single path without worrying about overwriting your whole store
You could have a kind for "structured data", like they use in activity pub and solid (but hopefully we can do better)
Then you have a json payload, and the type goes in the JSON
Then you could do aggregate queries from whatever list you want:
nostr.group('follows').get('store/items')
A new message kind for products on sale could be a nice idea, that's true.
One for offers and another one for requests.
These message kinds should then be used by different implementations of online shops (webs & apps). An eventual #nostr-uber and friends could use these same kinds
