@ Craig
Your analogy breaks down because Servers are not open and commonly understood platforms to which certain areas are restricted - as in your apartment block. Instead consider the following analogy:
Each apartment block you consider to rent has plug sockets for power and telecommunications. Some of them adhere to open standards - the common three pin power socket, BT socket (if you live in the UK) or RJ-10 for telephone, and RJ-45 for data. These are well known and the standard is available everywhere, so you can plug in any appliance that needs these sockets. The wiring behind them is kept away from you (do YOU know the new Europe-wide colouring scheme for mains wiring? Or the standard connections for RJ-45? I thought not), but you know the common interface.
Now consider an apartment block where the owner decides (arbitrarily) the size and shape of each socket. So if you want to plug in a fridge or a computer, you have to ask the owner to fit the right plug (which will then be hiddne behind a blanking plate, so you can't discover the shape of the plug for future reference). And what if the same owner built a newer block, where the sockets changed again, so you couldn't even move your appliances to the new block without getting the owner to refit the plugs (at great expense). And what if he didn't like the brand of fridge you wanted to use, and so refused to fit the correct plugs on your behalf? That, as I see it, is a much closer analogy to the MS Server API issue. No-one is suggesting that the source code be made available, just the methods for interfacing with the server OS efficiently.
And to extend the metaphor, what if the rent included a hefty charge to use the television provided with the apartment - even if you replaced it with a model you prefer? Surely you would like the option to take the television or not?
No, I think the EU got it right, assuming they can stick to their guns.