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. 

ok, so what you are saying here is that poser supports DSON right? that it is just my opinion that it does not? ok.(I never said poser did not, i said SM do not)
A light weight format does not mean less capable. - by providing an API that allows a plug-in to support it (mostly) so it supports it MOSTLY but is not less capable? Since when is that not a contradiction?

I hope you were not claiming to be any kind of expert on the topic, because right there, you lost it.

You stated that it was a Fact that SM does not support DSON. That is not in any way a fact. You then went on to back up your "fact" with a series of obvious opinions. 

SM has only one software product line, out of many, which would have anything to do with DSON. Did you want to talk about StuffIt instead? If so, you are correct Stuffit does not support Content from Renderosity or DAZ 3D, whether it is a CR2 or DSON. 

"A light weight format does not mean less capable. - by providing an API that allows a plug-in to support it (mostly) so it supports it MOSTLY but is not less capable?"

Two different statements, not related. I should have been more clear. Poser does not natively support the DSON format at this time....  Is that clearer? 

You appear to be reading things and misunderstanding. Let me try again. I am saying that Poser's API supports the ability to build an importer to import the format (which is support of the format). There are some issues with it, mostly due to the nature of that API. Native Import should work significantly better because it doesn't have to go through the Python API.