How are the DMIS Part 2 objects defined from the Part 1 specification?
Some of the DMIS statements (and other components of the DMIS specification, such as information from sections 2 and 3) map naturally to objects; others map to operations on these objects. Additional objects, methods, and asynchronous event notification are needed for interactive online communication with a language-based engine in a distributed client environment. By way of example, features map naturally to an object hierarchy: a base Feature class derives into FeatNom (nominal) and FeatAct (calculated actual or substitute feature) classes, which are further subclassed into FeatArc, FeatAArc, FeatCircle, FeatACircle, etc. A similar hierarchy is derived for Tolerances and Sensors; and many other DMIS types, like Carriages and Rotary Tables map to objects as well. The data members for a FeatCircle are already defined by the specification, which identifies each of them within the Input Format; while the Output Format identifies the data members for a FeatACircle. This is an example of h
