http://docs.daz3d.com/doku.php/public/dson_spec/start

This format is not intended to be fully backward compatible with Poser content, although extensive efforts have been made to accommodate features of the Poser file format for features that are common to Poser and DAZ Studio.

Ok - from the Keyboard of DAZ to your eyes. Enough about DSON already. It's old.

Which is stating that Poser Content, such as Victoria 4, is not fully compatible with the format. It is not stating that Poser could not import the format, or that Content in that format could not be used in Poser, given the DSON importer for Poser or Poser adding a native importer. 

That may be the case, but the fact remains, it was not meant to work completely in poser. And DSON offers a lightweight (read diminished) ability to use it in poser. Thanks, but IF, I should ever want to use it, I want to use it with no restrictions, So I would use DS. I personally don't care what the DSON argument is about, SM do not support it (and before you fanboys argue, go ask them a question about it.), fair enough, move to the software that does. In the end, no amount of extolling it's virtues, from however high you can climb, is likely to get them to change their minds. And TBH, with the amount of times poser threads have been hijacked by the DAZDSON fanboys, It would not surprise me in the least if the next version of poser dropped any kind of import support for DSON (we can only dream), and partnered up with Hivewire to make content. That way at least, DAZ will be able to charge for their studio software (touted to be worth $500); the arguments will end, and peace could return to the 3D world, and poser could actually move on to new things away from the (almost) constant argument that is DAZ in a poser forum.

Not a fact, your opinion. A light weight format does not mean less capable.

Poser does not natively support it, at this time, which does not equal to Poser does not support it, by providing an API that allows a plug-in to support it (mostly). That does not preclude Poser from supporting it in the future, nor does it mean that many Poser Users do not want Poser to support it natively.