The specification says that moving model dataset structure is based on the DIS standard however it is independent of the DIS standard. Which leads me to believe that Appendix M has the CDB moving model dataset structure. However, appendix M seems to be missing entries. For example, Appendix M's 1_Anti-Air does not mention any categories. (The XML published with the CDBAPI seems to be more complete.)

It would also be very nice if the moving model name structure was in something other than a PDF which is hard to parse. Could the name structure be provided in a xml or csv file?

It would also be very nice if the moving model name structure was in something other than a PDF which is hard to parse. Could the name structure be provided in a xml or csv file?

A possibly useful reference:

XoDIS XML Overview Message

Draft 0.3 of machine readable DIS enumerations (XML and XML Schema)

The specification says that moving model dataset structure is based on the DIS standard however it is independent of the DIS standard. Which leads me to believe that Appendix M has the CDB moving model dataset structure. However, appendix M seems to be missing entries. For example, Appendix M's 1_Anti-Air does not mention any categories. (The XML published with the CDBAPI seems to be more complete.)

The DIS Level 4 Categories for your 1_Anti-Air example are covered by Appendix M via inheritance, as implied by the (with subordinate hierarchy) comment, from those level 4 categories presented under the first entry for the corresponding DIS Level 2 Domain. In this case, that is 2_Munitions\0_Other (Level 1 Entity Kind\Level 2 Domain) which lists four level 4 categories: 0_Other, 1_Guided, 2_Ballistic, 3_Fixed which are applicable to the entire 2_Munitions hierarchy. As such, I believe that Appendix M of the CDB 3.0 specification is complete down to DIS Level 4 with respect to your question as is asserted by the excerpt below. If that is not the case, please either explain why, or provide another suitable example.

However, I do agree that the statement about DIS standard independence:

3.1.3.1 MModelGeometry Dataset Directory

The MModelGeometry Dataset is structured in a six-level hierarchy and is based on the DIS standard IEEE 1278.1-1995 (reference [4]). Note; however, that the CDB specification is independent the DIS standard.

As explained in reference [4], platforms models (a.k.a. moving models) are organized into a hierarchy that follows the DIS entity type structure hierarchy. As a recap, the DIS entity type is made of 7 fields named:

1. entity kind

2. domain

3. country

4. category

5. subcategory

6. specific

7. extra

The first four classification fields (kind, domain, country and category) are used to classify the moving models and map to directory level 2, 3, 4, and 5. Each of the classification fields is composed of a DIS classification code (1 to 3 character), followed by a DIS classification string representing the DIS classification name. The classification string is concatenated to the DIS classification code using the “_” (underscore) character to form the directory name. Appendix M specifies the list of DIS classification codes and the DIS classification strings supported by the CDB specification.

The last level directory name is created by concatenating each of the DIS classification codes with the “_” character. This also forms the moving model DIS Code.

[4] Enumeration and Bit Encoded Values for use with Protocols for Distributed Interactive Simulation Applications. Document number IST-CF-03-01. Institute for Simulation and Training, University of Central Florida. May 5th, 2004

The document can be obtained from the Simulation Interoperability Standards Organization at the following address:http://www.sisostds.org/. This document accompanies IEEE Std 1278.1-1995 and IEEE Std 1278.1A-1998.

is difficult to justify given that DIS Levels 5-7 are required for the last level directory name (CDB directory level 6), and also for the model file names, yet these DIS levels appear to be undefined by the CDB specification and its appendices, except by the external DIS specification reference [4].

The DIS Level 4 Categories for your 1_Anti-Air example are covered by Appendix M via inheritance, as implied by the (with subordinate hierarchy) comment, from those level 4 categories presented under the first entry for the corresponding DIS Level 2 Domain. In this case, that is 2_Munitions\0_Other (Level 1 Entity Kind\Level 2 Domain) which lists four level 4 categories: 0_Other, 1_Guided, 2_Ballistic, 3_Fixed which are applicable to the entire 2_Munitions hierarchy. As such, I believe that Appendix M of the CDB 3.0 specification is complete down to DIS Level 4 with respect to your question as is asserted by the excerpt below. If that is not the case, please either explain why, or provide another suitable example.

If someone who has a decent understanding about DIS can comprehend that then what I originally mentioned is fine.

On the other hand, names that are too long are cut off via the cell boundary. For example Country 222 is 222_Commonwealth_of_Independe and it stops there. There are a few other cases like that as well.