When you have a proprietary implementation competing with an open, compatible, one, you can have two scenarios:
1- the proprietary implementation is the dominant one and the open implementation must lag behind its roadmap.
2- the open implementation is dominant and the proprietary vendors who want to compete with it have to offer a superset of its functionality in order to compete.
In case 1, you are at the mercy of the proprietary implementor (in this case, Oracle). In case 2, everybody is free to steer the evolution of the standard without fear of getting isolated in an incompatible niche.
And Oracle's #1 priority is Oracle's profit. They'll get it even if it means turning your life into hell.
1- the proprietary implementation is the dominant one and the open implementation must lag behind its roadmap.
2- the open implementation is dominant and the proprietary vendors who want to compete with it have to offer a superset of its functionality in order to compete.
In case 1, you are at the mercy of the proprietary implementor (in this case, Oracle). In case 2, everybody is free to steer the evolution of the standard without fear of getting isolated in an incompatible niche.
And Oracle's #1 priority is Oracle's profit. They'll get it even if it means turning your life into hell.