Just my two cents,
In my opinion, for any standard, the key will be to define the standard in such a way that it can be implemented in any number of ways by organizations that choose to adopt it. That way, individual organizations or players are responsible to ensure that they are adopting the standard effectively and neither are constrained to a hard set of rules that they may not be comfortable following. It will be best to define things in terms of limits that NQ have placed on various things, which we will know by release.
For example, let's say that someone wants to make a standard for communications while docking. Let's say that the organization wants everyone that wants to land to use a specific encryption solution that they have written. Who is going to land at their spaceport? No one, because who knows what type of weirdness might be in that code (tracking code, killswitches, etc), especially if it can access the internet. The better way would be to say "all pilots need to use X encryption algorithm". Let's use RSA for our purposes. All organizations that want to adopt the standard can either get an implementation from the internet that they trust, or write one. Then, when a player wants to land (assuming they can also encrypt using RSA - they are responsible for ensuring that they can), they can ask the spaceport for its public key and then, having received it, begin the docking process. This is just an example.
Ultimately, it will be up to individual organizations to decide whether they want to follow any standard at all.