Unfortunately, the computer industry is full of organisations that suffer from NIH (not invented here) syndrome.
So if one company comes up with a good idea (in this case, Sybase/Microsoft and data type rules defined in the DB schema), the odds are pretty slim of getting a) the other 'mainstream' vendors (e.g. arch-nemesis Oracle in this case) and b) Academia (because there will be some philosophical problem with the implementation), to endorse the idea or move to get the idea formalized into the relevant standard.
What is more likely to happen is that the SQL standards 'committee of experts' come up with something that will include some of the concepts, but is sufficiently different from what has already been developed by the 'inventor' that the 'inventor' doesn't get any kind of perceived or actual advantage in the marketplace by having come up with the idea first. In the mean time, the competitors will be setting about coming up with something 'better'.
In the end, the standards body will come up something so arcane and obtuse that nobody bothers to use it, or they use vendor-specific 'versions' because they're easier and 'more efficient'.