i.e. several modules, covering different aspects of the information exchange, can be provided to the RTI. A number of predefined classes, datatypes, dimensions and transportation types are provided in the standard. These are provided in the HLAstandardMIM.xml FOM module. Predefined concepts are prefixed with HLA, for example HLAobjectRoot and HLAunicodeString. There are three different XML Schemas for the OMT: The OMT DIF XML Schema, that verifies that an OMT document follows the basic OMT format, but not that it is complete and has referential integrity. The OMT FDD XML Schema, that verifies that an OMT document contains enough information to be useful by an RTI. Note that this schema is provided in the Interface Specification. The OMT Conformance Schema that verifies that an OMT document is complete and has referential integrity. Identification Table The purpose of the identification table is to provide meta-data about the model, to facilitate reuse of the FOM/SOM or federates. The following fields are specified: General: Name, Type (FOM/SOM), Version, Modification date, Security classification, Release restriction, Purpose, Application domain, Description, Use limitation and Use history Keywords: Keyword values and Taxonomy used Point of contacts (POC): Type (Primary author/Contributor/Proponent/Sponsor/Release Authority/Technical POC), POC name, POC organization, POC telephone, POC email References: Type (Text document/Spreadsheet/Powerpoint file/Standalone FOM/Dependency FOM/Composed from FOM), Identification (document name or FOM name) Other Glyph (Icon) Object Classes Structure Table The purpose of the object class structure table is to specify the class hierarchy (subclass/superclass) of the object classes that are used to instantiate objects in an HLA federation. Object class attributes are inherited from superclasses to subclasses based on this hierarchy. The root of the object class tree is known as HLAobjectRoot. An example of a fully qualified name of an object class is HLAobjectRoot.Car.ElectricCar The following fields are specified for an object class in the hierarchy: Name Publication (Publish/Subscribe/PublishSubscribe/Neither) Attribute Table The purpose of the attribute table is to specify the attributes that are available for a given object class. Since attributes are inherited, an object class will have the union of all attributes that are locally defined on the object class or specified on any direct or indirect superclass. The following fields are specified for an attribute Object class name, for which it is defined Attribute name Datatype, defined in the Datatypes Table (see below) Update type (Static/Periodic/Conditional/NA) Update condition D/A (Divest/Acquire/NoTransfer/DivestAcquire): Whether the attribute can be divested and or acquired using the