Correct -- and that's a good thing. Maybe they won't b!tch it up so badly if they know where they're aiming for. Maybe.
Of course, this line from the article is bullcrap:
> ...the aim of making its market-dominating software products more compatible with those of competitors.
No, documenting the APIs doesn't "make software products more compatible with competition" -- that would require changing the software products. I don't think anybody is requiring changes in the code, and this is not a source release requirement. Microsoft must DOCUMENT how to call functions, and only at a fairly high level, too. What's the big freakin' deal?
Oh I know. Microsoft is embarrassed to have to show the competition how lame, redundant, spurious, confused, and bogus its APIs really are...
The claim is that Microsoft has lots of APIs that nobody else knows about. Thus their products can use the APIs to get better functionality than the competition. So if Microsoft makes monopoly-power Client A and someone else makes Server B, Microsoft will have an unfair advantage when they release Server C that functions better with A than B does because it uses the secret APIs (and any variation on that theme).