Standards versions backwards compatible compatibility break specification

What does OASIS do about backwards compatibility?

I recently was asked about how our TCs deal with backwards compatibility.

For those who don't spend their life with their nose in code, this is what happens when someone publishes a new version of a data standard, like FooML v2.0, but it does some things differently than did FooML v1.0...

Syndicate content