There's a pretty big gulf between software / OS interoperability and data / protocol interoperability. Think about cars. You can take a vehicle manufactured fo

There's a pretty big gulf between software / OS interoperability and data / protocol interoperability. Think about cars. You can take a vehicle manufactured for US market and take it to, say, Japan, but it won't be a smooth experience. Being in an environment so different requires you to (for want of a better word) "emulate" your way to adaptability. Cars in US have the wheel on left-hand side. Cars in Japan have the wheel on the right-hand side. But modulo emission limits[ß], their engines and transmission systems are mostly interchangeable. The final product, the car, is analogue for software. The inner plumbing, the components that make the product actually offer its functionality, is analogue for data and protocols. ß: Yes, I know. There are a whole lot of other requirements and regional regulations to consider too.