Leap Year Babies born on 29 February are attacking Microsoft for trying to standardise their leap year bug in OOXML. I guess the leap year is still in the standard after the BRM because standards needs to be tailored for a large dominant vendor.

Peter Brouwer, a spokesman for the Honor Society, says he's not surprised by the Invalid birth date bug, “Many Americans don't understand leap year – so why should the Internet?” Brouwer doesn't want to see a repeat of the leap year bug, which has taken over 20 years to correct. “In that bug, 1900 was counted as a leap year, even though it was not a leap year. Only recently has there been an agreement to fix the bug, when an international standards organization got involved. Brouwer says “We would be very proud if everyone used our software to fix their leap year bugs.“

What the press release does not tell us is if the 1900 bug is still in the OOXML specification after the BRM. I guess the leap year is still in the standard after the BRM because standards needs to be tailored for a large dominant vendor.