HLA Ownership Services P/S (Publish/Subscribe/PublishSubscribe/Neither): Whether the attribute can be published and/or subscribed. In a SOM, this information relates to the Federate described, in a FOM it relates to the entire federation. Available Dimensions Transportation (Reliable/BestEffort/other transportations described in the Transportation table) Order (Receive/TimeStamp): Delivery order for attribute updates. Interaction Class Structure Table The purpose of the interaction class structure table is to specify the class hierarchy (subclass/superclass) of the interaction classes that are used to exchange interactions in an HLA federation. Interaction class parameters are inherited from superclasses to subclasses based on this hierarchy. The root of the interaction class tree is known as HLAinteractionRoot. An example of a fully qualified name of an interaction class is HLAinteractionRoot.CarCommand.Start. The following fields are specified for an interaction class in the hierarchy: Name Publication (Publish/Subscribe/PublishSubscribe/Neither) Parameter Table The purpose of the parameter table is to specify the parameters that are available for a given interaction class. Since parameters are inherited, an interaction class will have the union of all parameters that are locally defined on the interaction class or specified on any direct or indirect superclass. Dimensions table The purpose of the dimensions table is to specify the DDM dimensions, used for attributes and interaction classes. Time representation table The purpose of the time representation table is to specify the datatypes used by the Time Management services. User-supplied tag table A user-supplied tag can be supplied when calling certain HLA services. The purpose of the user-supplied tag table is to specify the datatypes of these tags. Synchronization table The purpose of the synchronization table is to specify the synchronisation points used in a federation. Transportation type table The purpose of the transportation type table is to specify the available transportation types. There are two predefined transportation types: HLAreliable and HLAbestEffort. Update rate table The purpose of the update rate table is to specify the available maximum update rates. Switches table The runtime behaviour of the RTI can be controlled using a number of predefined switches. The purpose of the switches table is to provide initial values for these switches. Some of the switches can also be updated at runtime. Datatypes The purpose of the datatype tables is to provide specifications of the datatypes used for attributes, parameters, dimensions, time representation, user supplied tag and synchronization points. There are six categories of datatypes, with a separate tabular format for each of them.