Hi Billy,
I've had the same problem - I'm working with older version of the product (9.1,9.5), so can't comment on whether the missing elements are present in the schema for the newer versions. Looking at the xsd's I got the impression that the schemas were generated from example management module xml files using altova xml spy, and that perhaps the xml used didn't contain the ADS element, hence it being missing in the generated XSD - could be totally wrong though!
This was an issue when marshalling/unmarshalling jaxb bindings - so I resorted to adding the ADS definition back into the xsd manually prior to running the jaxb compilation just to get the complete set of objects.
Would be very interested to find out if this has been resolved.
Cheers,
Iain