Indigenous solutions typically develop differently for a reason. Building standards in a wet humid climate prone to flooding differ from those in the desert because they have different needs: if you make a standard set of guidelines that applies universally, it will inherently need to be more complicated than the guidelines adapted for a specific scenario.
Part of the brilliance of the internet is the way things are layered; you can have all kinds of different solutions for different layers while keeping things interoperable. If Australia has a different wifi standard than America, it doesn’t mean they can’t connect.
While I understand the impulse to have some central body moderate unproductive standards wars, if you enforce overly strict standards by law you stagnate industries whether you’re trying to capture them.
Just imagine how much time and effort would be wasted trying to get every software engineer to use the same programming language. Arguably it would lead to way less duplicated effort, but you’re never going to get everyone to agree on all aspects of the language. And that’s as it should be; people should have the freedom to chose what works best for them.
If we’re smart and focus more on building base, opt in, very generic/low level infrastructure that can federate responsibility and adapt to differing higher level standards rather than getting everyone on the same set of high level standards, I think we’re better off.
I’m not sure exactly what the regulatory equivalent of a tcp/ip layer would be, but some sort of very basic, fill in the blanks kind of regulatory template would be better than enforcing various discrete world standards.