Introduction

1.1 Name

The name of this component is "xj3d_DIS". This name shall be used when referring to this component in the COMPONENT statement (see 7.2.5.4 Component statement). It is an extension to the current DIS component

1.2 Overview

This clause describes the DIS component of this part of ISO/IEC 19775. This includes how to describe additional clipping planes of for objects to provide sectioned views of the object. Table 1 provides links to the major topics in this clause.

2 Concepts

2.1 Overview

28.3 Node reference

28.3.2 DISEntityManager

DISEntityManager : X3DChildNode {
  SFString   [in,out] address                                    "localhost"
  SFInt32    [in,out] applicationID                              1         [0,65535]
  MFNode     [in,out] mapping                                    []        [DISEntityTypeMapping]
  SFNode     [in,out] metadata                                   NULL      [X3DMetadataObject]
  SFInt32    [in,out] port                                       0         [0,65535]
  SFInt32    [in,out] siteID                                     0         [0,65535]
  MFNode     [out]    addedEntities
  MFNode     [out]    removedEntities
}

The mapping field provides a mechanism for automatically creating an X3D model for a new entity arriving. If a new entity matches one of the nodes then an instance of the provide URL will be created and added as a child to the EspduTransform specified in the addedEntities. See the DISEntityMapping node for details on matching DIS parameters to URLS.

The addedEntities field contains any new entities added last frame. These will be EspduTransform nodes.

The removedEntities field contains any entities removed last frame, either from a timeout or from an explicit removeEntityPdu. This will contain a reference to the EspduTransform node.

28.3.3 DISEntityTypeMapping

DISEntityTypeMapping : X3DInfoNode {
  SFInt32    []       kind                            0         [0,255]
  SFInt32    []       domain                          0         [0,255]
  SFInt32    []       country                         0         [0,65535]
  SFInt32    []       category                        0         [0,255]
  SFInt32    []       subcategory                     0         [0,255]
  SFInt32    []       specific                        0         [0,255]
  SFInt32    []       extra                           0         [0,255]
  MFString   [in,out] url                             []
}

The fields are checked in the following order: kind, domain, country, category, subcategory, specific, extra.

Given an entity whose entity type record was: kind=1, domain=2, country=3, category=4, subcategory=5, specifc=6,extra=7. If the mapping field of the DISEntityManager contained these nodes:

   DISEntityMapping {
      domain 1
      kind 2
      country 3
      url ["model-a.x3d"]
   }
   DISEntityMapping {
      domain 1
      kind 2
      country 3
      category 4
      url ["model-b.x3d"]
   }

28.4 Support levels

The DIS component provides one level of support as specified in Table 28.2.