Sure - I just think that we do ourselves a disservice by not making it clear when something is due to Microsoft's requirements rather than due to the standard. Standards (however much influenced by corporate interests) are a powerful force in many people's views, and one often needs a good reason to diverge from them; so let's not invest Microsoft's policy with the further force of standards for them, when in fact in this case the standard doesn't specify a particular policy.