I never indicated that the definition couldn't include open implementations, just that the definition wasn't limited to ONLY openness. There are plenty of examples of this behavior not even exclusive to Microsoft. Proprietary products can build on an open protocol and attempt to change it, sometimes for the worse.

I didn't bring Skype into this, so I'm not going to comment on it as an example.