As you can see, even between ISO specifications, there is a difference in how IP issues are handled. If the open source community wishes to take advantage of this, then you'll need to get in and work the system to your advantage. We've done it once before with VRML, so there is no reason why it cannot be done again with new specifications. If you don't like MP3's problems, then a community driven effort is certainly possible and can work within international standards frameworks. You just need to find the right one to work with.
Enforceable security is one.
Each standard includes a minimum conformance section to make sure of the level playing field. The only problem that you face then is that ISO likes to have some formal body to represent the developers of that spec - not particularly difficult given the thousands of these that already exist in the opensource world. Just some more formal wrappers are needed. In some areas this is certainly the case, but in the computing industry this is far from the norm. I don't know what the licensing will be for this, but I'll bet the MPEG committee won't make that mistake again.