Prove me wrong: You can't just write standards. All you've got is a shot at drafting schemas and crossing your fingers the market adopts them

Builder of Context Protocol. https://www.ctx.xyz

Not really. Standards are usually drafted in collaboration with their intended users and undergo revisions to accommodate for new needs. That's why standards include an RFC stage and are often revised when needs change for one reason or the other.

Dad, geek, entrepreneur. Conversation liquidity provider. vrypan.net (home), @weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

What's the difference between builders and market? Take HTTP for example, aren't Google, Microsoft, Mozilla, etc. the "builders"? Who is the community when it comes to the next USB or HDMI standard? That's why I said "intended users". May be a couple of hackers for ERC-20 in 2015, or a few mega-corps for HDMI.

I find more practical a bottom-up approach, where builders create schemas and evolve them along market adoption.

But is not community who turns this proposals into standards?