Yeah, atproto pushes this down to be a community/governance issue. Nobody is preventing apps from working out a common standard and supporting it. However, nobody is forcing them to do that either. So it will play out with natural dynamics. What atproto ensures is that there's a convention for strongly-typed foward-evolving schemas and how they get validated (and reverse domains specify the authority). But ultimately cooperation is up to the community.