2006 CCRTS Command and Control Research and Technology Symposium The State of the Art and the State of the Practice

June 20 – 22, 2006 San Diego, CA

Topic:

C2 Experimentation

Title:

An Object-Oriented XML Schema for the MIP Joint Command, Control, and Consultation Information Exchange Data Model

Authors: Name: Organization: Address: Phone: Fax: E-Mail: Name: Organization: Address: E-Mail: Name: Organization: Address: E-Mail:

Michael Gerz FGAN/FKIE Neuenahrer Straße 20 53343 Wachtberg-Werthhoven, Germany +49 228 9435 414 +49 228 9435 685 [email protected] Francisco Loaiza Institute for Defense Analyses 4850 Mark Center Drive, Alexandria, VA, 22311, United States [email protected] Erik Chaum Defense Modeling and Simulation Office 1901 North Beauregard Street, Suite 500, Alexandria, VA, 22311, United States [email protected]

Form Approved OMB No. 0704-0188

Report Documentation Page

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

1. REPORT DATE

3. DATES COVERED 2. REPORT TYPE

JUN 2006

00-00-2006 to 00-00-2006

4. TITLE AND SUBTITLE

5a. CONTRACT NUMBER

An Object-Oriented XML Schema for the MIP Joint Command, Control, and Consultation Information Exchange Data Model

5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S)

5d. PROJECT NUMBER 5e. TASK NUMBER 5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES)

8. PERFORMING ORGANIZATION REPORT NUMBER

Institute for Defense Analyses,4850 Mark Center Drive,Alexandria,VA,22311 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES)

10. SPONSOR/MONITOR’S ACRONYM(S) 11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT

Approved for public release; distribution unlimited 13. SUPPLEMENTARY NOTES

The original document contains color images. 14. ABSTRACT 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF:

17. LIMITATION OF ABSTRACT

a. REPORT

b. ABSTRACT

c. THIS PAGE

unclassified

unclassified

unclassified

18. NUMBER OF PAGES

19a. NAME OF RESPONSIBLE PERSON

67

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

An Object-Oriented XML Schema for the MIP Joint Command, Control, and Consultation Information Exchange Data Model Michael Gerz, Francisco Loaiza, Erik Chaum

Semantic interoperability among command and control information systems is critical to information sharing and proper automated processing. To improve multinational combined and joint mission capabilities, the Multilateral Interoperability Programme (MIP) has defined the Joint Command, Control, and Consultation Information Exchange Data Model (JC3IEDM), which is gaining wide acceptance beyond the MIP community. In this paper, we present a reference XML schema definition (XSD) that has become an integral part of the JC3IEDM 3.0 specification. It provides an objectoriented view on the data model and aims at simplifying and accelerating the adoption of the MIP data model in service-oriented architectures and web application development. We provide the use cases and design principles that have lead to this XSD. Moreover, we show how this type of XML schema can be obtained in an automated way from any relational schema in third normal form by applying only structural and syntactic transformative rules. The application of the XSD is demonstrated by instance XML documents that describe an operational scenario. Keywords: XML, XML Schema, XSD, Multilateral Interoperability Programme, MIP, JC3IEDM, STANAG 5525

1. Introduction Semantic interoperability among command and control information systems (C2IS) is critical to information sharing and effective automated processing. To improve multinational combined and joint mission capabilities, a voluntary multinational community of interest (COI) has developed and worked over many years to address the fundamentally difficult task of building community consensus and semantic standards for command and control information exchange. This work is being done by the Multilateral Interoperability Programme (MIP; http://www.MIP-site.org) which is currently comprised of 25 nations, the North Atlantic Treaty Organization (NATO), and the US Allied Command Transformation (ACT). The MIP documents its conceptual and semantic consensus in an entity-relationship data model, the most recent of which is the Joint Command, Control, and Consultation Information Exchange Data Model (JC3IEDM; see MIP, 2005). The JC3IEDM and its predecessor, the C2IEDM, are gaining wide acceptance beyond the MIP community as a foundational core component for command and control semantic interoperability. The JC3IEDM edition 3.0 was published by the MIP in December 2005. Its adoption 1

1. Introduction CANDIDATE-TARGET-LIST

RULE-OF-ENGAGEMENT

REPORTING-DATA CAPABILITY

ACTION

REFERENCE CONTEXT

VERTICAL-DISTANCE

OBJECT-TYPE

OBJECT-ITEM

LOCATION

COORDINATE-SYSTEM

AFFILIATION

GROUP-CHARACTERISTIC

ADDRESS

Figure 1: JC3IEDM Independent Entities (IDEF1X Notation) by NATO, and the ongoing NATO ratification as STANAG 5525, will strongly influence the development of future C2ISs. The JC3IEDM has a very rich capability to express both operational and tactical context. Much more than a simple tactical picture, the MIP’s operational analysis process has defined a set of information exchange requirements that support the commander across a spectrum of types of operations and activities (e.g., planning, coordination, execution, observing, and decision making). Figure 1 shows a high-level independent entity-relationship view of the JC3IEDM. The C2IEDM and JC3IEDM have the essential common characteristic of being generic (i.e., not derived directly from system-specific implementations) and extensible (i.e., suitable as a core to which functional extensions can be added). This last point is critical because without a shared core set of concepts and semantics each functional community of interest will build unique incompatible representations of the battlespace. This results in higher costs to develop and integrate systems and services and results in limited information exchange and automated processing capabilities due to the limitations of mediation (i.e., mapping or translating). If mediation produces a complete and precisely equivalent representation then the mapping was completely syntactic (i.e., the exact same representation was developed twice – a low probability event). Most often this is not the case and mapping and translation are incomplete, imprecise, contextually loose, and produce an ambiguous result. This limits interoperability, the users’ trust and understanding of the information being shared, and in the end operational effectiveness. Recently, many national and international projects have been initiated to explore the benefits of XML technologies and Web Services in the C2 area. Exposing unique semantics in XML does not address the fundamental limitations of mediation. While XML simplifies the processing of documents by means of a uniform syntax, there is still a need to have a common understanding of the information to be exchanged, i.e., the set, and structure, of the XML elements used for information exchange and their semantics have to be defined. 2

Information models are essentially specifications of semantics and syntax. Thus, it makes sense to use the JC3IEDM as a multinational, system-independent standard for XML C2 semantics. To avoid diverging and incompatible exchange formats in each individual project, there should be reference XML schema definitions (XSDs) based on the data structures contained in the JC3IEDM. The MIP community has addressed this demand by developing two standardized XML schemas.1 The first reference MIP XML schema, namely the RDBMS XSD, reflects the relational view of the JC3IEDM. It addresses information exchanges among relational databases whose physical schemas are based on the JC3IEDM specifications. The design of the second reference MIP schema has been motivated by the perceived need to support Web Service (WS) applications within the C2 community. It provides an object-oriented view of the data model and aims at simplifying and accelerating the adoption of the MIP data model in service-oriented architectures and web application development. The object-oriented reference MIP XML schema (WS/OO XSD) does not make any assumptions on the physical storage of operational data and yet allows checking many of the referential integrity constraints of the JC3IEDM during instance XML document validation. These features make the WS/OO XSD very attractive to applications that do not necessarily rely on, or need a JC3IEDM-compliant relational database (e.g., for persistence), or which do but desire to present an object-oriented exchange service. It should be noted that the design rationale for both XML schemas and their associated technical artifacts are now part of the official JC3IEDM 3.0 specification. In this paper, we present the object-oriented reference MIP XML schema. In section 2, we provide the use cases and requirements that have lead to the WS/OO XSD. In section 3, we show how this type of XSD can be obtained from any relational schema in third normal form by applying only structural and syntactic transformative rules. The generality of this approach enables the model and XSD to be extended by functional communities. The application of the WS/OO XSD is demonstrated by an operational scenario in which a contingency plan for a composed military obstacle is generated, and updated (section 4 and appendix A). Based on the example, we show that the WS/OO XML schema is not restricted to one particular information exchange mechanism. In section 5, we describe a tool kit that allows, in an automatic way, deriving the XSD and corresponding Java classes. The paper closes with a summary in section 6.

2. XML Use Cases and Schema Requirements XML is a universal information exchange syntax with wide acceptance in industry. It can be used in various types of applications and use cases. In the context of MIP, six potential use cases were identified: • Data exchange: – Web Services (e.g., exchange of business objects). – Exchange with non-MIP databases. – MIP XML Exchange Mechanism (exchange among MIP databases via XML). • Transformation services: 1

The results presented in this paper have been developed within the XML Working Party of the MIP. Apart from the authors, the members of the XML WP are (in alphabetical order): Fred Burkley (US, Naval Undersea Warfare Center), Gerald Ortner (NHQC3S, NDA), and Cecilia Unell (SE, Combitech AB).

3

2. XML Use Cases and Schema Requirements – Supporting tactical communications interfaces, e.g., ADatP-3 or USMTF (effectively almost always lossy). – Mediation between different versions of the MIP data model. – Export to various output/presentation formats, e.g., STANAG 5500-conformant messages or HTML. It is recognized that an optimal schema design can only be achieved in the context of a specific set of detailed requirements. For each use case described above, we can derive different requirements on the XML schema. The requirements are partially contradictory, i.e., no single XML schema fits all purposes equally well. For instance, information exchange between MIP databases and mediation between different data model versions requires an XML schema that facilitates easy integration into MIP-compliant systems and a simple mapping to the JC3IEDM relational database schema. These requirements are met by the MIP RDBMS XSD. For information exchange via web services, the focus shifts to simple integration into object-oriented applications. Here, the strict technical adherence to a relational data model may be considered as a hindrance to efficient data processing. The WS/OO XML schema addresses this requirement. In the following, we discuss three factors from which we derive requirements on the XML schema design. These factors are (a) the type of sender/receiver of the XML message, (b) the information exchange mechanism, and (c) existing XML standards.

2.1. Requirements Derived from Sender/Receiver The sender/receiver of an XML message may either be a person, a generic XML viewer (e.g., a web browser), or a C2 information system. In the latter case, we can distinguish between systems that maintain a JC3IEDM-compliant relational database and systems that use a proprietary data model internally and make their data persistent in an arbitrary way, e.g., in an object-oriented data base. Systems that do not store their data in a MIP-compliant RDBMS can greatly benefit from an XML schema that abstracts from the relational data model. The same holds for systems that use the JC3IEDM data base schema but for which the MIP Data Exchange Mechanism (DEM) is replaced or complemented by web services. To support modern software development, an XML schema with an object-oriented view on the MIP IEDM is highly desirable. Developers will also require that code fragments, which comply with the XML schema (e.g., Java classes), can be generated efficiently. If there is no back-end RDBMS to enforce the MIP data model semantics (in particular referential integrity), the XML schema should include semantic constraints for domain values, document consistency (no orphan objects), and, ideally, the JC3IEDM business rules. These can be checked during instance XML document validation. In a mixed MIP/non-MIP environment, syntactic and semantic transformations are inevitable. The combination of XSL-T and an implementation-neutral object-oriented schema provides a technically mature application path for gateways that mediate between the different worlds. When the sender/receiver is a person, an XML tag naming convention must ensure ease of readability and comprehension. Software developers working with the XML documents and associated code classes will also benefit from such naming conventions. 4

2.2. Requirements Derived from Information Exchange Mechanism

2.2. Requirements Derived from Information Exchange Mechanism There are several possible ways in which systems and/or people may exchange information. We distinguish between three different information exchange mechanisms: • Message-based communication • Replication-based communication • Query-based communication In the first case, instance XML documents describe referentially complete, self-contained messages.2 For message-based communication, the XSD must ensure referential integrity within a single XML document according to the rules of the data model. Moreover, the XSD for the MIP IEDM must be generic in that it must be possible to tailor it to specific business object XSDs. In a replication-based scenario, an initial data load is exchanged and then incremental information updates are transmitted (push technology). For instance, only status updates may be sent, once the corresponding unit has been transmitted. When a receiver queries data from a provider (pull technology), the query results may not necessarily be complete either. For example, a web client requests information on what units are in a given geographic region. In response, the client receives a report that mentions unit Bravo is at location Alpha as of time Tango. The user subsequently wants to know Bravo’s current location. Thus, the web client must be able to refer to Bravo by means of a ’key’ (e.g., object identifier, URL, or similar) and the web service must be able to provide a position report update on request, which only contains the information that has changed. There may also be cases in which the query result contains references to objects that are not yet known to the web client. This just-in-time, interactive, pull for relevant data is consistent with web services concepts and complementary to the traditional MIP smart push architecture. The referential integrity and completeness required by the MIP IEDM has implications for the design of XML schemas and associated web services. The latter two use cases require a reference mechanism such that instance documents can refer to external information. However, one need not necessarily retain all of the synthetic keys of the MIP data model for that purpose. The referential integrity constraints in the XSD that hold for message-based communication must be relaxed in replication- and query-based use cases. It is the responsibility of the web service and client – not of the XSD! – to ensure that external references are used appropriately.

2.3. Requirements Derived from XML Standards In order to facilitate the validation of XML documents, the XML document format must be formalized by means of an XML schema. The schema itself is specified in a schema language. There are many different schema languages available with varying expressiveness and complexity. An overview of existing schema languages is given by van der Vlist (2001). Currently, the most prominent schema language is XML Schema (W3C, 2004a,b,c). It is the one adopted for the MIP WS/OO XML schema.3 It is standardized by the World Wide Web Consortium (W3C) 2

This approach has been adopted by the MIP MEM and the ADatP-3 community before. However, the definition of hundreds of message text formats (MTF) resulted in a variety of different representations for basic information like time and date. Self-contained XML messages based on the JC3IEDM resolve the problem as the entities of the MIP IEDM define standard data elements (SDE). 3 In the following, the term XML Schema is written in small capitals if it refers to the specification language itself. Otherwise, it refers to the concrete WS/OO XML schema.

5

3. XML Schema Design and supported by virtually all XML tool vendors. The W3C XML Schema is based on an object-oriented model, i.e., it allows defining types and using inheritance. Fundamental to achieving multinational and joint network-enabled capability (net-centric or network-enabled operations) is a common structure and language for information handling. XML does not support interoperability automatically. Today, there are hundreds of XML vocabularies; a fact which may account in part for the limited improvement in semantic interoperability despite the commonality of syntax. Therefore, while XML provides new tools for improving point-topoint translations, the long-term objective and big win comes through semantic harmonization. To that effect, Naming and Design Rules (NDR) are being developed at the international, multinational and national levels. Their intent is to facilitate the discovery and use of common data elements (standardized XML vocabulary), and to provide additional rigor to the XML standards in order to maximize interoperability and enhance supportability. NDRs specify various aspects of an XML schema: naming of XML elements and attributes, schema versioning, schema modularization, definition of namespaces, (restricted) use of XML Schema constructs, etc. NDRs are mainly concerned with the structure and reusability of XML schemas; they do not answer completely what instance XML documents should look like for a particular use case. In the WS/OO XML schema, the Guidance for XML Naming and Design within NATO (GXND; currently only in draft) was applied where practical. The GXND is based on two standards: ISO/IEC 11179 (Metadata Registries, MDR; see ISO/IEC, 2005) and ISO 15000-5 (Electronic business eXtensible Markup Language, ebXML; see ISO, 2005).

3. XML Schema Design Based on the requirements listed in the previous section, we have developed the reference MIP WS/OO XSD. Structures in instance XML documents conforming to the WS/OO XSD closely match the typical OO concepts, e.g., inheritance and navigability. In particular, the representation of relationships and associations via nesting greatly simplifies the adoption of the MIP IEDM in object-oriented applications. To describe (potentially cyclic) graph structures in the tree-like XML notation, a simple mechanism for referencing objects is provided. Instance XML documents exchanged in accordance with the WS/OO XSD do not prescribe any specific storage format, i.e., the WS/OO XML schema abstracts from the underlying persistence mechanism. This matches with the notion of defining an XML exchange format. Developers are able to choose any persistence framework, API, or tool, which simplifies integration. The XML schema is fully automatically derivable from the MIP IDEF1X (see Wikipedia, 2006b) model by applying syntactic transformations only. In that way, the generation is independent from a particular version of the MIP data model. This approach ensures correctness and minimizes XSD production and maintenance cost. If we had relied on the specific semantics of a particular version of the MIP data model to drive the transformations, we would have had to check the mapping rules as the model changed over time. Moreover, transforms must be traceable – the more we transform away from the relational model, the more difficult it becomes to specify and apply the transformation rules and to prove their correctness. The WS/OO XSD is primarily based on the logical view of the MIP JC3IEDM. The physical view of the data model contains a few additional MIP DEM-specific attributes and is designed for an RDBMS implementation. However, all types of web-services should be supportable by the WS/OO XSD, which is more readily accomplished when basing the specification on the semantics of the logical view of the MIP IEDM. 6

3.1. Naming Conventions In this section, the mapping rules are described that are applied to the MIP data model in order to produce the object-oriented XML schema. These rules create a faithful representation of the model. The focus of the following description is on what instance XML documents look like rather than on the technical details of the XML schema definition. The WS/OO XSD comes along with a tool set (see section 5), such that the whole transformation process – starting with the MIP data model in ERwin XML format and ending with the XML schema files – is traceable. The WS/OO XSD and the tool set are available at the MIP web site and considered a normative part of the reference MIP WS/OO XSD specification. For a complete mapping, transformation rules must be defined for names, domains, entities, attributes, and relationships (including subtyping and associative entities). Moreover, the root element of XML documents must be specified. The mapping rules are described in detail in the following subsections. The MIP XML Working Party worked through a process whereby entity-relationship (ER) modeling constructs were interpreted into UML and then interpreted into an XML design pattern.

3.1. Naming Conventions To ensure consistency and reproducibility, naming conventions are needed for entities, attributes, and the root element visible in instance XML documents, as well as for simple types, codes, and entity types that only show up in the XML schema definition. Naming of domains, entity types, and attributes in XML is based on the logical view rather than on the physical view of the MIP data model. This enhances readability and comprehension. In accordance with the NATO Naming Guidelines, the UpperCamelCase convention is used for naming XML elements and XML types, whereas the lowerCamelCase convention is used for naming XML attributes.

3.2. Domains Domains in the ER model are mapped onto XML simple types. The latter are derived from the pre-defined XML Schema types integer, double, and string. Physical restrictions on JC3IEDM domains, i.e., the number of digits for integers, the precision and scale of floating point numbers, and the minimum/maximum length of character strings are reflected in the XSD. Where available, specific range restrictions (e.g., maximum temperature or non-negative quantity) are regarded as well. The upper and lower boundary of numbers is modeled by the XML Schema attributes minInclusive and maxInclusive. The minimum and maximum length of strings is modeled by means of the attributes minLength and maxLength. Codes are represented as strings that are restricted by enumeration. JC3IEDM code values are specified as physical values rather than display values in an instance XML document. This is motivated by efficiency with regard to bandwidth, software development and object persistency. The mapping from the physical values to display values is a matter of national language preference and can be realized easily by means of an XSL-T script. The display values documented by the MIP data model (international English) are included as annotations in the XSD for convenience.

3.3. Entities and Attributes Entity types in the MIP IEDM are mapped onto complex types in the XML schema definition. In conformance with the NATO XML Naming and Design Rules, attributes in the ER model are specified as XML elements, not XML attributes, exclusively. This simplified approach removes 7

3. XML Schema Design Design Pattern IDEF1X

A a-id a-some-attr-1 a-some-attr-2 a-some-attr-3 (FK)

UML

XML



. . . . . . . . .

. . . [relationships]

[relationships]

Figure 2: Entities and Attributes the arbitrary or even semantic decision about when to use what. Accordingly, an entity is described by an element with child elements for its attributes in an instance XML document (see figure 2). Optionality of attributes in the MIP IEDM is maintained by means of the XML Schema minOccurs attribute. Non-key attributes are mapped to XML elements by applying the above-mentioned naming conventions. Whenever possible, the entity type name, which is added as a prefix for the attribute names in the logical view, is truncated. This rule conforms to the class and property conventions used in object-oriented programming, i.e., the meaning of an XML element is derived from its context. Primary and foreign key attributes (i.e., identifiers and indexes) are not mapped directly. Instead, the transformation patterns for relationships (see next section) are applied. Object Identifiers. In the WS/OO XSD, globally unique object identifiers (OIDs) replace the synthetic primary keys of the MIP data model. The global uniqueness of OIDs simplifies integration into object-oriented applications. An OID is a sequence of characters that allows an application locating and managing (persistent) objects. In the context of the world-wide web, an OID may be a URI (Uniform Resource Identifier). In this case, the OID denotes a web address that can be used to refer and retrieve the object, and the closure of all IEDM objects forms a localized semantic web of their own. In the WS/OO XSD, OIDs are defined for all types that either correspond to independent entity types in the ER model or have list elements and thus need to be referable for future updates. Whether an XSD type has an OID is determined after applying the transformation patterns for relationships and associations. References. At any place in an instance XML document where it is possible to specify an entity with an OID (inline), it is also possible to specify a reference to that entity. Both options are included (a) to provide support for various instance document styles, (b) to handle graph 8

3.4. Transformation Rules for Relationships Design Pattern IDEF1X

A

B

a-id

a-id (FK)

UML A

B

-bList[0..*] : B 1

XML

0..*

. . . (inline) . . . (by reference) ...

Figure 3: Identifying Relationships structures, and (c) to allow for both referentially complete and incremental update information exchange methods. References are indicated by adding suffix Ref to the name of the XML element (e.g., UnitRef or ReportingOrganisationRef ). Beside its OID, an entity reference has neither elements (entity attributes) of simple type nor of code type. However, an entity reference can be used to describe a new relationship of the referred entity with another one. For instance, a new OrganisationStatus may be specified inside a UnitRef element (see next section for the modeling of relationships). XML binding tools/frameworks like JAXB (Sun Developer Network, 2006), Castor (exolab.org, 2006), or Commons Betwixt (Jakarta Project, 2006) use XML’s ID/IDREF mechanism to serialize graph structures. However, please note that ID/IDREF can only be used as a referencing mechanism for referentially complete documents but not when exchanging incremental updates. The XML schema definition is available in two variants: with and without identity constraints, i.e., checks for internal referential completeness. The WS/OO XSD that includes the identity constraints enforces a corresponding entity definition for every reference. These entities must be defined by a child element of the root element. The identity constraints are specified in a way that ensures type-safe referential integrity of instance XML documents (ID/IDREF would not provide type-safety). The constraints are defined as part of the XML root element definition (see section 3.5).

3.4. Transformation Rules for Relationships 3.4.1. Identifying and Non-Identifying Relationships In IDEF1X, the modeling technique and notation used for the MIP IEDM, there are two basic types of relationships: identifying and non-identifying relationships. They correspond to oneto-one and one-to-many associations between classes in UML where the associations may be navigable in either both directions or one direction. In most cases, a link is established from the parent to its child only. An identifying relationship means that the child cannot be uniquely identified without the parent. For example, an OBJECT-ITEM-STATUS cannot exist without its OBJECT-ITEM. In an ER 9

3. XML Schema Design Design Pattern IDEF1X

A

B

b-id b-id (FK)

UML A

B

-b[0..1] : B *

XML

0..1

. . . (inline) or . . . (by reference)

Figure 4: Non-Identifying Relationships model, an identifying relationship is modeled by a primary key in the child that is also a foreign key referring to the parent. Identifying relationships are modeled in the WS/OO XSD according to the design pattern shown in figure 3: A new list element, called B List, is embedded into the parent entity, which again encompasses multiple B elements. If possible, the name of the parent is stripped from the names of the elements. Example: The one-to-many relationship between an OBJECT -ITEM and an OBJECT -ITEM-STATUS is modeled in XML by StatusList and Status elements. (Note: strictly speaking List elements are not required but are included for clarity). Depending on the cardinality of the relationship (zero-one-or-more, one-or-more, zero-or-one), the list element may be absent or contain one or more definitions of child entity B. The cardinality of identifying relationships is ensured by adding minOccurs and maxOccurs attributes to the corresponding definitions in the XSD. Please note that List elements may also occur within entity references (e.g., within ObjectItemRef ). This allows adding information on new relationships to entities that have been defined/exchanged before. In entity references, minOccurs is always set to 0. A non-identifying relationship is one where the child can be identified independently of the parent. For instance, an Organisation can exist independently from a ReportingData that refers to it as the reporting organization. The transformation of non-identifying relationships is shown in figure 4. The optionality (null allowed vs. no null) of non-identifying relationships is expressed by minOccurs attributes in the WS/OO XSD. 3.4.2. Subtype Relationships In instance XML documents, subtyping relationships are represented by embedding all the attributes from a subtype hierarchy within the tag corresponding to the leaf entity (see figure 5). In the WS/OO XML schema definition, the complex type for the sub-entity is derived from the complex type for the super entity by means of the extension method of XML Schema. Functional COIs may tailor individual types either by further extension or by restriction. In IDEF1X, the subtype is indicated by a discriminator code (category code) in the super type. In WS/OO instance XML documents, category codes do not have to be specified in general, as 10

3.4. Transformation Rules for Relationships Design Pattern IDEF1X

A

B

a-id

a-category-code

b-id (FK)

a-category-code

UML A

XML

B

. . . . . . ... . . . ...

Figure 5: Subtype Relationships they are implied by the subtype tag itself. However, in the case of incomplete subtyping, the discriminator code must be specified if it does not correspond to one of the existing sub-entities (this holds for codes like NOS – Not Otherwise Specified ). 3.4.3. Many-to-Many Relationships – Associative Entities In relational models, a many-to-many relationship between two entities A and B is expressed by an associative entity A-B-ASSOC that is the child of both A and B via identifying relationships. In the MIP IEDM, all many-to-many-relationships are binary. Nevertheless, we can distinguish three cases: • Associative entities with only primary key attributes • Associative entities with non-primary key attributes • Double-associative entities An associative entity with only primary key (PK) attributes is equivalent in UML to a simple association between the two parent classes. Each parent may have a list of references to instances of the other class. This view is also reflected in the design pattern given in figure 6. Associative entities without non-PK attributes are not mapped onto the XML schema. The relationships from parent A to A-B-ASSOC and from parent B to A-B-ASSOC are mapped as if they were identifying relationships from A to B and vice versa. Note that since there is no preferred direction in the association, either entity can be nested inside the other in XML. If the associative entity has non-primary key attributes, it corresponds in UML to an attributed association with an association class that contains the attributes. There are several ways to represent such many-to-many relationships in XML (see, e.g., Williams, 2002). For the WS/OO XSD, a design pattern is applied that allows embedding the association into either parent (see figure 7). For that purpose a list element (ABAssocInAList) is introduced. It contains tuples consisting of the associated second parent of type B and the associative entity that holds the association attributes. The ability to describe associations by nesting rather than by a top-level element avoids information scattering throughout XML documents and enhances readability. Moreover, the WS/OO 11

3. XML Schema Design

Design Pattern IDEF1X

A

A-B-ASSOC

a-id

B

a-id (FK) b-id (FK)

b-id

UML A

B

-bList[0..*] : B

-aList[0..*] : A 0..*

XML

0..*







. . . (inline)

. . . (inline)

. . . (by ref .)

. . . (by ref .) ...

...









Figure 6: Associative Entities With Only PK Attributes

Design Pattern IDEF1X

A

A-B-ASSOC

a-id

B

a-id (FK) b-id (FK)

b-id

some-attr

UML A-B-ASSOC

*

A

XML

*

B













. . . . . .

. . . . . .













. . . ...

Figure 7: Associative Entities With Non-PK Attributes

12

3.5. XML Root Element Design Pattern IDEF1X

A-ASSOC

A

subject-a-id (FK) object-a-id (FK)

a-id

some-attr

UML

* A

A-ASSOC *

XML









. . .

. . .

. . .

. . .









Figure 8: Double-Associative Entities XSD supports object-to-association reasoning rather than association-to-object reasoning. This is considered as an important prerequisite for the compact definition of community-specific message formats that are derived from the generic XSD by tailoring. It should be noted that the representation of associations in XML documents may differ from the internal representation in applications. For instance, the XML parser mentioned in section 5 generates Java objects that support navigability in either directions (A → ABAssoc → B and B →ABAssoc → A). There are also associations in which both relationships come from the same entity type. The generic syntactic transformations for such associations are similar to the transformations for associative entities with non-PK attributes given above. The only difference is that the element names include generic role names for the associated entities (see figure 8). Subject and Object are used as (model-independent) role names. The suffixes are necessary, because in an XML document the object may be embedded in the subject and vice versa.

3.5. XML Root Element The root XML tag is equivalent to the model name in capital letters (). The distinction between different model versions is made by means of the name space, whose URN, among others, incorporates the model version number. The root XML element has an arbitrary number of unordered XML entity definitions as child elements. The names of the child elements are identical to the names of the corresponding entity types (e.g., Unit or ReportingDataAbsoluteTiming). Each child must have a non-abstract and referable type. Non-abstract entity types do not have a subtype. For instance, ObjectItem is abstract whereas MinefieldLand is not. (In case of incomplete subtyping, the super type can be regarded as non-abstract as well). Referable entity types have an object identifier (OID) attribute. An instance XML document with five top-level entity definitions is shown in listing 1 on page 15. 13

4. XML Example

N

Obstacle Alpha White Horse Bridge

West Minefield

East Minefield

Yukon River

S Figure 9: Obstacle Alpha

4. XML Example In the following, the use of the object-oriented XML schema is illustrated by the operational scenario described in chapter 9.6 of the JC3IEDM main document (MIP, 2005, p. 246). For convenience, it is recapitulated in section 4.1. The modeling of the vignette by means of the JC3IEDM is described in section 4.2. Excerpts from the corresponding instance XML documents are explained in section 4.3. For the complete documents, please see appendix A.

4.1. Operational Scenario The JC3IEDM main document defines an operational scenario in which the 1st Canadian Brigade is located near a bridge across the Yukon River. Its contingency plan is to use this bridge as part of a larger military obstacle, called Obstacle Alpha: ”The White Horse Bridge across the Yukon River initially serves as a passage between two minefields located on the north side of the river, one on each side of the bridge. [...] If the units of the joint task force that are now deployed on the north side of the river need to withdraw, the bridge will be demolished to become part of the main obstacle.” (MIP, 2005, p. 246)

The operational picture is shown in figure 9. During the hostilities, the 1st CA Brigade is attacked and the contingency plan is put into action. The complete course of actions is as follows: Reporting Time

Action

22 Oct 2003, 10:30

1 CA Brigade creates the contingency plan to set up Obstacle Alpha which consists of the two minefields and the bridge to be demolished. Minefield West is laid and activated. Minefield East is laid and activated. The White Horse Bridge is prepared for demolition. The brigade elements north of the river cross to the south. The bridge is demolished and Obstacle Alpha becomes operational in its entirety.

02 03 03 07

Nov Nov Nov Nov

2003, 2003, 2003, 2003,

09:49 15:42 17:10 08:10

4.2. JC3IEDM Modeling In the JC3IEDM, the two minefields are modeled by means of entity type MINEFIELD-LAND. The White Horse Bridge is an instance of entity type BRIDGE and Obstacle Alpha is a MILITARY-OBSTACLE. 14

4.3. Instance XML Documents 1 2

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

OI1 West Minefield ... 300 105 Minefield West 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI2 East Minefield ... OI3 White Horse Bridge ... OI4 Obstacle Alpha ... RPTD705 ... ...

Listing 1: Top-level elements

Since all entities are facilities, their statuses are described by means of entity type FACILITYSTATUS. Both the White Horse Bridge and Obstacle Alpha have two status objects assigned to them, because their statuses change over time. Initially, the bridge is operational and prepared for plan execution while Obstacle Alpha is merely planned. Once White Horse Bridge is demolished, Obstacle Alpha is declared as operational and active. All status information is associated with either a REPORTING-DATA or a REPORTING-DATA-ABSOLUTE-TIMING. The composition of Obstacle Alpha is modeled by instances of OBJECT-ITEM-ASSOCIATION and OBJECT-ITEM-ASSOCIATION-STATUS.

The overall data structure for the vignette is given as a UML object diagram in appendix A.1 on page 23. The granularity and expressive richness of the JC3IEDM can be seen by this example. The symbol colors indicate the different times of creation of the corresponding objects. In total, the vignette is modeled by 41 objects. With a JC3IEDM-compliant RDBMS, the effective number of database records would be significantly higher, since, e.g., the information for a land minefield is physically stored in five different tables (OBJECT-ITEM, FACILITY, MILITARYOBSTACLE, MINEFIELD, and MINEFIELD-LAND). 15

4. XML Example 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

OI1 West Minefield OT1 RPTD001 FR RPTD701 REP RPTFCT 20031102094900.000 ... YES OPR ACTIVE NOS 300 105 ...

Listing 2: Status information

4.3. Instance XML Documents The overall structure of an XML document for the above-mentioned vignette is shown in listing 1. It is a referentially complete document that covers the whole history of Obstacle Alpha. On the top level, the main objects of the operational scenario, i.e., West Minefield, East Minefield, White Horse Bridge, Obstacle Alpha, etc. are defined. Each object is described coherently by a single element rather than by records in multiple tables as when using the MIP DEM. For instance, all attributes of a MinefieldLand – including those inherited from entity types Facility and ObjectItem – are specified at a single place in the document (lines 3–16). All objects shown above have a globally unique object identifier (OID). This allows referring to them from a different object in the same XML document or from another XML document in order to establish an association. In the previous excerpt, only the basic attributes were listed for the West Minefield. In reality, its definition also includes a status and a type. In the JC3IEDM ER model, they are linked to the minefield by means of identifying relationships and associative entities. Their modeling in XML is illustrated in listing 2. Since a MinefieldLand can have multiple statuses (one-to-zero-one-ormore relationship), the status is wrapped in a StatusList element that may contain an arbitrary number of status definitions (lines 16–31). The relationship between the West Minefield and its status is established by embedding the latter into the definition of the former. By means of nesting, it is not necessary to specify the OID of the West Minefield within the status definition as required by the JC3IEDM ER model – the link between both entities is derived implicitly from the document structure. 16

4.3. Instance XML Documents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

OI1 West Minefield ... FR RPTD701 ... OI6 ... ... ... OI6 1 CA Bde ... 1 CA Bde

Listing 3: References

Listing 2 also shows that not all elements have an OID. Unlike the minefield, the minefield status is not referable. Whereas the minefield may get a new status later and thus there must be a way to refer to it, the status object itself cannot be changed in the future. In general, only those entities to which information may be added later have an OID. Among others, the 15 independent entity types of the JC3IEDM (including their sub-entity types) and associations whose status is subject to change have an OID attribute. Finally, listing 2 illustrates the application of the polymorphism concept. According to the JC3IEDM entity-relationship model (disregarding business rules), an object item can be associated with any record of the status hierarchy, e.g., a FacilityStatus, a MedicalFacilityStatus, or a PersonStatus. Similarly, we can refer to different kinds of ReportingData (ReportingData, ReportingDataAbsoluteTiming, ReportingDataRelativeTiming) within a status. In order to support document validation, one has to specify the concrete type that is actually used. This is done by means of attribute xsi:type (XSI = XML Schema Instance). For instance, in line 19, we specify xsi:type=”ReportingDataAbsoluteTiming” to define a ReportingData with absolute timing information. Nesting of entities is not restricted to a certain level. In listing 2, ReportingData is embedded in the Status element, which again is part of the West Minefield definition. In principle, structures may become very deeply nested or – in case of cyclic dependencies between objects – even infinitely. In these cases, the reference mechanism can be used which is revealed in listing 3.4 For every status update, the reporting organization must be specified as part of the reporting data. The status of the West Minefield is reported by the 1st Canadian Brigade. Rather than embedding the ReportingOrganisation inside the MinefieldLand /StatusList/Status/ReportingData structure, a reference is made by means of a ReportingOrganisationRef element (lines 11– 13) that only contains the OID of the organization to which it refers. The unit is defined as a separate top-level element in the XML document (lines 21–26). In case of a reference, there is 4

If for some arbitrary reason communities choose to avoid deep nesting in all cases, this can be accomplished through functional community business rules applied at the namespace or specific business object level.

17

5. Tool Support 1 2

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

OI1 FR ... YES OPR ACTIVE NOS

Listing 4: Incremental update

no need to specify the concrete subtype. In the example above, no xsi:type attribute is required in line 11, although the ReportingOrganisationRef is in fact a reference to a Unit. In the given example, the 1st CA Bde is specified at the end of the XML document. However, the XML schema makes no assumptions on the order of top-level elements, i.e., an object may be defined ahead of its reference. As explained in section 2.2, there are several possible ways in which communication may take place. The generic WS/OO XML schema is designed in a way that it can be used in all scenarios described above. In message-based communication, the constraints in the WS/OO XSD ensure referential integrity within a single XML document: whenever a reference is made, a corresponding definition must be given. For instance, an XSD validation tool is able to check that there is indeed a reporting organization for the minefield status. The corresponding constraints are type-safe, i.e., the schema validator will complain if you refer to a non-Organization object accidentally. For incremental updates and incomplete queries, the referencing mechanism can be used to refer to information defined externally. This is illustrated in listing 4. In this document, a status update is reported for the object with OID OI1 (= West Minefield). In addition to an OID, an Ref element may contain an arbitrary number of list elements. In that way, you can establish new associations with existing objects.

5. Tool Support A tool set has been developed to support the generation and application of the WS/OO XSD. The software, which was developed at the Research Institute for Communication, Information Processing and Ergonomics, FGAN FKIE, Germany, comprises the following components: • A combined WS/OO schema and Java source code generator. • A set of model-independent Java base classes that complement the Java class library. • An XML parser that processes (unmarshalls) instance XML documents. • Supplementary tools for validating and pretty-printing XML documents. 18

The toolkit is based on the Java 5.0 specification and provided as an Eclipse 3.1 project (Eclipse Foundation, 2006). The XML schema and Java code generation is carried out in three steps: 1. The MIP IEDM meta model is read from a file in ERwin XML format and stored in an internal data structure.5 2. Various automated transformations are applied to the meta model in order to realize the design patterns described in section 3. Among others, these transformations include the removal of key attributes, the selective addition of OID attributes, and the introduction of list attributes for identifying relationships. 3. Based on the modified meta model, two different outputs are produced: Modular WS/OO XSD — It is provided as five files that contain the schema definitions for the entities, codes, and simple types of the MIP IEDM, as well as the definition of the XML root element (with and without identity constraints that ensure referential integrity). The physical partition of the XSD improves maintenance, design, and reuse. The XSD is available in two versions: a schema definition with annotations (i.e., additional comments) and a stripped-down version for more efficient processing. Java class library — It consists of a large number of class files that are grouped into three packages (entity, code, and simple). The Java classes are structurally equivalent to the type definitions in the XSD with the exception of associations that are represented differently to support navigation in both directions (from subject to object and vice versa). To demonstrate that MIP WS/OO instance documents can be validated and processed efficiently, we developed an XML parser that reads data in XML and creates and initializes corresponding Java objects. The parser is based on the Simple API for XML (SAX), which is a component of the Java API for XML Processing (JAXP ; Sun Microsystems, 2006). SAX parsing is event-driven: whenever an XML element begins or ends, a corresponding callback function is invoked. Unlike the DOM (Document Object Model), SAX allows reading XML documents incrementally (stream processing). This means that there is no need to keep the complete XML document in memory. In order to process WS/OO instance documents, it is sufficient to maintain an information stack whose size increases and decreases with varying nesting level of XML elements. The XML parser is generic in that it does not require meta model information. Object creation and manipulation is based on the Java reflection mechanism that allows calling methods by name at run-time. The core of the XML parser comprises about 250 lines of code. To simplify processing, the parser makes use of some fixed attributes by which XML documents are enriched during schema validation. For instance, any List element has a typeCategoryCode attribute with fixed value AssociationList. Fixed attributes make it possible to identify elements that describe entities, associations, and lists without having to rely on tag naming conventions or meta model information. The MIP WS/OO XSD already comes along with specifications for various fixed attributes. Additional fixed attributes might further simplify the processing of associations. Developers are free to introduce such attributes in the MIP XSD for internal purposes, as long as the attributes do not show up in exchanged instance documents. The development of the parser has proven that the potentially deep nesting of XML elements does not impose any technical burden and – given a suitable internal object representation – 5

The generator tool expects XML output of ERwin 4.1.4 Service Pack 3 (i.e., version 4.1.4.4224), the version of Computer Associate’s data modeling tool that is used by the MIP. Unfortunately, the ERwin XML format is not stable. We noticed that it changed even with service packs.

19

6. Summary and Conclusion the referencing mechanism can be handled in a simple way. Processing of associations also proved to be unproblematic even though their representation in XML documents differs from the representation in the Java classes (where links are introduced from the associating entity to the associated objects). The XML parser also demonstrates that incremental updates can be handled easily. For instance, reading the referentially complete XML document in appendix A.2 results in the same internal Java object representation as consecutively loading all partial XML documents from appendix A.3. The tools and the XML/Java products that they generate are available at the MIP homepage (MIP, 2006). They are provided under the Berkeley Software Distribution (BSD) license (Wikipedia, 2006a), i.e., they can be used freely in both non-commercial and commercial projects.

6. Summary and Conclusion In this paper, we have presented the reference MIP WS/OO XSD that is conformant with the logical model of the JC3IEDM. The MIP IEDM is driven by a C2 Community of Interest and provides a system-independent view of information exchange requirements. Likewise, the WS/OO XSD provides a system-neutral representation suited for exchange. The WS/OO XSD is designed in a way that it is extensible by other functional communities. All functional communities (surveillance, logistics, fires, anti-submarine warfare, artillery, modeling and simulation, testing, etc.) semantically overlap command and control. Thus extending the C2 logical model (and XSD) as required with community unique concepts and semantics ensures that all functional commanders and processes can receive and understand the commander’s intent and provide feedback as required. Technically, extensions can be made in two ways: by complementing the XSD with manually defined complex types (possibly derived from existing types) or by extending the MIP ER model and re-running the XSD generation tool. The XML schema and its accompanying products described in this paper present a reference baseline suitable for supporting a broad scope of XML application and service development work. Currently, XML schemas are available for both the JC3IEDM 3.0 and the C2IEDM 6.15e. They are being published in the public space to encourage use of the MIP IEDM semantics and to serve as a catalyst for MIP capability development using XML. MIP also intends to make submissions to the forthcoming NATO XML Registry. The explicit purpose of MIP continuing with the development of XML reference capabilities is not to replace or dictate national development efforts, but rather, to significantly lower the barrier for those interested in learning and implement MIP-capable XML services and applications. The WS/OO XSD satisfies the needs of various information exchange mechanisms. Semantic checks for valid domain values, optional/mandatory attributes, and document consistency allow thorough validation before processing the data. With the JC3IEDM as a sound semantic foundation, the XML schema builds a bridge between message-based and replication-based information exchanges. Areas of future work include the formal representation of JC3IEDM business rules. For instance, the XSD does not check for legal code combinations. Unfortunately, the expressiveness of XML Schema is too limited to describe such business rules. A language which focuses on the specification of semantic checks is Schematron (see ISO/IEC, 2004). Unlike XML Schema, which is used to describe the structure of XML documents, Schematron follows a rule-based approach. It can be used as a supplement to XML Schema. 20

References

References Eclipse Foundation (2006). Eclipse Software Development Kit. http://www.eclipse.org/. 19 exolab.org (2006). Castor – Open Source data binding framework for Java. http://www.castor. org/. 9 ISO – International Organization for Standardization (2005). ISO/TS 15000-5:2005 Electronic Business Extensible Markup Language (ebXML) – Part 5: ebXML Core Components Technical Specification, Version 2.01 (ebCCTS). Available through the ISO store at http://www.iso.org/. Also available for free as UN/CEFACT CCTS V2.01 (http: //www.unece.org/cefact/ebxml/CCTS_V2-01_Final.pdf). 6 ISO/IEC – International Organization for Standardization/International Electrotechnical Commission (2004). ISO/IEC FDIS 19757-3, Rule-based validation – Schematron. http: //www.schematron.org. 20 ISO/IEC – International Organization for Standardization/International Electrotechnical Commission (2005). ISO/IEC 11179, Information Technology – Metadata Registries (MDR). All ISO/IEC 11179 standards are available for free at http://metadata-standards.org/. 6 Jakarta Project (2006). Commons Betwixt – Turning beans into XML. http://jakarta. apache.org/commons/betwixt/index.html. 9 MIP – Multilateral Interoperability Programme (2005). The Joint C3 Information Exchange Data Model (JC3IEDM Main), Edition 3.0. http://www.mip-site.org. 1, 14 MIP – Multilateral Interoperability Programme (2006). mip-site.org/. 20

MIP Home Page.

http://www.

Sun Developer Network (2006). Java Architecture for XML Binding (JAXB). http://java. sun.com/webservices/jaxb/. 9 Sun Microsystems (2006). Java API for XML Processing (JAXP) 1.3. http://java.sun.com/ webservices/jaxp/index.jsp. 19 van der Vlist, E. (2001). Comparing XML Schema Languages. O’Reilly xml.com, http://www. xml.com/pub/a/2001/12/12/schemacompare.html. 5 W3C (2004a). XML Schema Part 0: Primer Second Edition. W3C Recommendation. http: //www.w3.org/TR/2004/REC-xmlschema-0-20041028/. 5 W3C (2004b). XML Schema Part 1: Structures Second Edition. W3C Recommendation. http: //www.w3.org/TR/2004/REC-xmlschema-1-20041028/. 5 W3C (2004c). XML Schema Part 2: Datatypes Second Edition. W3C Recommendation. http: //www.w3.org/TR/2004/REC-xmlschema-2-20041028/. 5 Wikipedia (2006a). BSD license. Wikipedia, the free encyclopedia, http://en.wikipedia.org/ wiki/BSD_license. 20 Wikipedia (2006b). ICAM Definition Languages (IDEF). Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/IDEF. 6 Williams, K. (2002). XML for Data: Modeling many-to-many relationships. IBM developerWorks, http://www-128.ibm.com/developerworks/xml/library/x-xdm2m.html. 11 21

A. XML Example – Obstacle Alpha

A. XML Example – Obstacle Alpha In this appendix, the complete instance XML documents are presented for the vignette described in section 4 on page 14. The formal specification of the operational scenario by means of the JC3IEDM is shown in section A.1. The XML document in section A.2 describes the complete history of the operational scenario. The documents in section A.3 illustrate replication-based information exchange with incremental updates.

22

: ReportingData

: ReportingDataAbsoluteTiming OID = 702

: ReportingDataAbsoluteTiming

OID = 701

1 CA Bde : Unit

OID = OI6

: ObjectItemType

CA Brigade : UnitType

OID = OT6

Intelligence : Unit

OID = OI5

: ObjectItemType

Intelligence : UnitType

OID = OT5

OID = RPTD005

: ReportingDataAbsoluteTiming

: FacilityStatus

: FacilityStatus

OID = RPTD704

: ReportingData

: ObjectItemAssociationStatus

: ObjectItemAssociationStatus

: FacilityStatus

OID = 712

: ReportingDataAbsoluteTiming

OID = 711

: ReportingData

: ObjectItemAssociationStatus

: ObjectItemAssociationStatus

: ObjectItemAssociation OID = OIA1

: ObjectItemAssociationStatus

OID = OIA4

OID = OIA2

: ObjectItemAssociationStatus

: FacilityStatus

OID = OI4

Obstacle Alpha : MilitaryObstacle

: ObjectItemType

CompoundObstacle : MilitaryObstacleType OID = OT4

OID = RPTD703

: ObjectItemAssociation

OID = RPTD705

: ReportingDataAbsoluteTiming

: FacilityStatus

: ObjectItemAssociation

: ReportingData

: FacilityStatus

White Horse Bridge : Bridge OID = OI3

East Minefield : MinefieldLand

: ObjectItemType

OID = OI2

: ObjectItemType

West Minefield : MinefieldLand

OID = RPTD001

OID = OI1

: ObjectItemType

IronHorse : BridgeTyoe OID = OT3

LandMineField : ObjectType

OID = OT1

A.1. JC3IEDM Model

A.1. JC3IEDM Model

23

A. XML Example – Obstacle Alpha

A.2. Referentially Complete Document OI1 West Minefield OT1 RPTD001 FR RPTD701 REP RPTFCT 20031102094900.000 OI6 20031102094500.000 YES OPR ACTIVE NOS 300 105 Minefield West 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI2

24

A.2. Referentially Complete Document East Minefield OT1 RPTD001 FR RPTD702 REP RPTFCT 20031103154200.000 OI6 20031103153000.000 YES OPR ACTIVE NOS 320 90 Minefield East 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI3 White Horse Bridge OT3 RPTD001 FR RPTD704 REP RPTFCT 20031103171000.000 OI6 TIMNA

25

A. XML Example – Obstacle Alpha PRPEXE NO OPR PASABL NOS FR RPTD705 EXECTD NO NOP DSTRYD NOS 200 10 40 5 RLWYVH OI4 Obstacle Alpha OI1 OIA1 ISPART START RPTD711 START RPTD712 OI2 OIA2 ISPART START RPTD711 START RPTD712

26

A.2. Referentially Complete Document OI3 OIA4 ISPART START RPTD711 START RPTD712 OT4 RPTD001 FR RPTD703 PLAN RPTFCT 20031022103000.000 OI6 TIMNA YES NOP PRPEXE NOS FR RPTD705 YES OPR ACTIVE NOS

27

A. XML Example – Obstacle Alpha 650 325 NOS RPTD705 REP RPTFCT 20031107081000.000 OI6 20031107080000.000 RPTD711 PLAN RPTFCT 20031022103000.000 OI6 TIMNA RPTD712 REP RPTFCT 20031107081000.000 OI6 20031107080000.000 OT1 NO LandMinefield MINEFD OT3 NO Iron Horse CNTLVR OT4 NO Compound obstacle NOS RPTD001 REP RPTFCT 20031022103000.000 OI6 TIMNA

28

A.2. Referentially Complete Document OI6 1 CA Bde OT6 NO CA Brigade YES ARMY COMBAT INF BDE RPTD005 1 CA Bde OI5 Intelligence OT5 NO Intelligence NO JOINT COMSPT MILINT BDE RPTD005 Intel RPTD005 REP 20020102000000.000 OI5 20020102000000.000

29

A. XML Example – Obstacle Alpha

A.3. Incremental Information Exchange A.3.1. Initial Type Information Exchange on 02 January 2002 OT1 NO LandMinefield MINEFD OT3 NO Iron Horse CNTLVR OT4 NO Compound obstacle NOS OI6 1 CA Bde OT6 NO CA Brigade YES ARMY COMBAT INF BDE RPTD005 1 CA Bde

30

A.3. Incremental Information Exchange OI5 Intelligence OT5 NO Intelligence NO JOINT COMSPT MILINT BDE RPTD005 Intel RPTD005 REP 20020102000000.000 OI5 20020102000000.000

A.3.2. Contingency Plan Creation on 22 October 2003 OI1 West Minefield OT1 RPTD001

31

A. XML Example – Obstacle Alpha 300 105 Minefield West 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI2 East Minefield OT1 RPTD001 320 90 Minefield East 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI3 White Horse Bridge OT3 RPTD001 200 10 40 5 RLWYVH OI4 Obstacle Alpha OI1

32

A.3. Incremental Information Exchange OIA1 ISPART START RPTD711 OI2 OIA2 ISPART START RPTD711 OI3 OIA4 ISPART START RPTD711 OT4 RPTD001 FR RPTD703 PLAN RPTFCT 20031022103000.000 OI6

33

A. XML Example – Obstacle Alpha TIMNA YES NOP PRPEXE NOS 650 325 NOS RPTD711 PLAN RPTFCT 20031022103000.000 OI6 TIMNA RPTD001 REP RPTFCT 20031022103000.000 OI6 TIMNA

A.3.3. Activation of Minefield West on 02 November 2003 OI1 FR RPTD701 REP RPTFCT

34

A.3. Incremental Information Exchange 20031102094900.000 OI6 20031102094500.000 YES OPR ACTIVE NOS

A.3.4. Activation of Minefield East on 03 November 2003 15:42 OI2 FR RPTD702 REP RPTFCT 20031103154200.000 OI6 20031103153000.000 YES OPR ACTIVE NOS

35

A. XML Example – Obstacle Alpha A.3.5. White Horse Bridge Prepared for Demolition on 03 November 2003 17:10 OI3 FR RPTD704 REP RPTFCT 20031103171000.000 OI6 TIMNA PRPEXE NO OPR PASABL NOS

A.3.6. Obstacle Alpha Becomes Operational on 07 November 2003

36

A.3. Incremental Information Exchange OI3 FR RPTD705 EXECTD NO NOP DSTRYD NOS OI4 OI1 OIA1 START RPTD712 OI2 OIA2 START RPTD712 OI3 OIA4 START RPTD712 FR

37

A. XML Example – Obstacle Alpha RPTD705 YES OPR ACTIVE NOS RPTD705 REP RPTFCT 20031107081000.000 OI6 20031107080000.000 RPTD712 REP RPTFCT 20031107081000.000 OI6 20031107080000.000

38

An Object-Oriented XML Schema for the MIP Joint Command, Control, and Consultation Information Exchange Data Model Michael Gerz, FGAN FKIE Erik Chaum, DMSO – Francisco Loaiza, IDA 2006 CCRTS June 20 – 22, 2006

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Overview „ „ „ „ „ „ „

Motivation MIP JC3IEDM Use Cases, Requirements & Design Principles Transformation Rules XML Example Tool Support Summary

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Motivation „ Multinational interest in the use of XML for C2 info exchange ‹ ‹

National and multinational projects NATO XML Registry

„ Semantic interoperability is critical to information sharing ‹

XML does not automatically ensure common understanding

„ Multilateral Interoperability Programme (MIP) ‹ ‹

‹

Voluntary multinational C2 Community of Interest (COI) Supported by 25 nations, NATO, and ACT

Defines the Joint Command, Control, and Consultation Information Exchange Data Model (JC3IEDM)

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

MIP Information Exchange Data Model action-id (FK) capability-id (FK)

is-quantified-in / quantifies

capability-id

*

ACTION

ACTION-REQUIRED-CAPABI

CAPABILITY

C2IEDM Edition 6.15 1 October 2004

capability-category-code capability-subcategory-cod capability-day-night-code capability-unit-of-measure-c

requires-as-a-minimum / is-minimum-required-for

requires / is-required-for

action-required-capability-qu is-quantified-in / quantifies

action-category-co action-name

action-id (FK) action-resource-index

action-functional-association-subject-actio action-functional-association-object-action action-functional-association-index

CANDIDATE-TARGET-LI

object-item-id (FK) capability-id (FK) object-item-capability-index

fire-capability-id (FK)

ammunition-type-id (F

engineering-capability-id (FK)

is-acted-upon-as-specified-by

action-id (FK) action-resource-index (FK)

action-id (FK) action-objective-index (FK)

candidate-target-list-id (FK) candidate-target-detail-index object-type-id (FK)

mission-capability-id (FK) is-quantified-in / quantifies

action-resource-employment-category-c

action-id (FK) action-objective-index (FK)

object-item-id (FK)

SURVEILLANCE-CAPABILITY

action-objective-item-marking-method-code action-objective-item-marking-panel-shape-code action-objective-item-marking-recognition-signal-c action-objective-item-marking-start-date action-objective-item-marking-start-time action-objective-item-marking-using-organisation-

target-engagement-authority-co target-vicinity-duration

ACTION-AIRCRAFT-EMPLOYMENT

ACTION-RESOURCE-TYPE action-id (FK) action-resource-index (FK)

action-id (FK) action-resource-index (FK)

action-resource-type-quantity action-resource-type-apportionment-frac object-type-id (FK)

action-aircraft-employment-approach-offset-code action-aircraft-employment-deplanement-method-code action-aircraft-employment-egress-direction-angle action-aircraft-employment-inflight-report-requirement-indica action-aircraft-employment-terminal-attack-direction-angle

is-recognised-as-having / is-ascribed-to Z TARGET-PERSONNEL-PROTECTION action-id (FK) action-objective-index (FK)

surveillance-capability-catego

is-the-user-of / is-used-by

target-personnel-protection-categoryreporting-data-id (FK)

STORAGE-CAPABILIT is-used-in-the-definition-of / storage-capability-id ( is-defined-with materiel-type-id (FK)

ORGANISATION-ACTION-ASSOCIATIO organisation-id (FK) action-id (FK) organisation-action-association-index

is-specified-as / is-specification-of is-specified-as-having / is-normal-quantity-stated-for

‹

provides-applicable-information-for / is-referenced-to

object-type-category-code object-type-dummy-indicator-c object-type-name

FEATURE-TYPE feature-type-id (FK) feature-type-category-cod

‹

feature-type-category-code

bridge-type-design-type-c MILITARY-OBSTACLE-TYPE military-obstacle-type-id (FK) military-obstacle-type-category-

materiel-type-id (FK)

is-assigned-lfril-code-in

‹

control-feature-type-id (FK) control-feature-type-category-co

EQUIPMENT-TYPE equipment-type-id (FK)

specifies

is-main-equipment-of / has-as-main-equipment

equipment-type-category-cod AIRCRAFT-TYPE aircraft-type-id (FK) aircraft-type-category-code aircraft-type-subcategory-co ELECTRONIC-EQUIPMENT-TYPE electronic-equipment-type-id (FK)

P

is-referenced-in / refers-to

organisation-structure-root-organisation-id organisation-structure-index

organisation-structure-root-organisation-id organisation-structure-index (FK) organisation-structure-detail-index

OBJECT-TYPE-AFFILIAT

is-configured-as-specified-in / specifies-the-configuration-of

includes / is-an-element-of

organisation-category-co organisation-nickname-n

biological-agent-type-id (FK)

biological-agent-type-category-code biological-agent-type-subcategory-code biological-agent-type-identification-num biological-agent-type-persistency-code

MISCELLANEOUS-EQUIPMENT-TYPE

chemical-agent-type-category-code chemical-agent-type-subcategory-code chemical-agent-type-identification-numb chemical-agent-type-persistency-code

object-type-establishment-effective-date object-type-establishment-category-code object-type-establishment-environment-condit object-type-establishment-name object-type-establishment-operational-mode-c

NUCLEAR-AGENT-TYPE RAILCAR-TYPE railcar-type-id (FK) railcar-type-category-code railcar-type-subcategory-c railcar-type-gauge-dimens

vehicle-type-id (FK) vehicle-type-category-c

nuclear-agent-type-category-code nuclear-agent-type-identification-numbe nuclear-agent-type-primary-radiation-co

reporting-data-id (FK)

facility-category-code facility-primary-construction-material facility-height-dimension facility-length-dimension facility-width-dimension

object-item-address-call-sign-text object-item-address-transmit-indicator reporting-data-id (FK)

ORGANISATION-TYPE

airfield-air-traffic-control-presence-indicator-code airfield-hangar-area-quantity airfield-instrument-landing-system-presence-indic airfield-aircraft-parking-area-quantity airfield-runway-lighting-presence-indicator-code airfield-runway-maximum-length-dimension airfield-runway-surface-type-code

object-item-object-type-establishment-effectiv

address-id (FK)

bridge-id (FK)

bridge-longest-span-length-dim bridge-span-quantity bridge-usage-code

is-referenced-in

physical-address-category-code physical-address-residence-text physical-address-street-text physical-address-street-additiona physical-address-postal-box-text physical-address-postbox-identifie physical-address-city-text physical-address-geographic-text physical-address-postal-code-tex

MASS-GRAVE

MATERIEL

organisation-type-category-code organisation-type-command-function-indicator-c organisation-type-command-and-control-catego organisation-type-description-text

materiel-serial-number-identificatio materiel-lot-identification-text materiel-body-colour-code materiel-marking-code materiel-marking-colour-code

AFFILIATION-ETHNIC-GRO

organisation-type-category-co

affiliation-id (FK) affiliation-ethnic-group-cod

CIVILIAN-POST-TYPE civilian-post-type-id (FK)

AFFILIATION-EXERCISE-GRO

civilian-post-type-category-

affiliation-exercise-group-nam

group-organisation-type-id (FK) group-organisation-type-category-

person-id (FK)

feature-id (FK)

affiliation-id (FK)

person-birth-date person-blood-type-cod person-ethnic-group-co person-gender-code person-religion-code

feature-category-cod

affiliation-functional-group-code affiliation-functional-group-name

PRIVATE-SECTOR-ORGANISATION-TYPE private-sector-organisation-type-id (FK) private-sector-organisation-type-category-co private-sector-organisation-type-main-activit

MASS-GRAVE-CONTENT

mass-grave-content-gender-co mass-grave-content-age-code mass-grave-content-quantity

PERSON

FEATURE AFFILIATION-FUNCTIONAL-GRO

contains / is-contained-by P

mass-grave-id (FK) mass-grave-content-index

has

affiliation-id (FK)

GROUP-ORGANISATION-TYPE

network-category-code network-subcategory-code network-architecture-code network-channel-count-quantity network-maximum-capacity-quantity network-minimum-capacity-quantity network-means-code network-cryptographic-indicator-code network-cryptographic-plan-short-titlenetwork-cryptographic-code-short-title network-security-classification-code network-security-classification-caveatnetwork-security-policy-code

mass-grave-id (FK

materiel-id (FK)

affiliation-category-cod

materiel-status-id (FK) object-item-status-index (FK)

military-obstacle-id (FK)

uses / is-specified-for

military-obstacle-category-

harbour-id (FK) harbour-approach-channel-depth-dimensi harbour-biologically-secure-availability-ind harbour-convoy-marshalling-indicator-cod harbour-fire-fighting-capability-code harbour-fire-fighting-indicator-code harbour-fresh-water-availability-indicator-c harbour-maximum-vessel-draught-dimens harbour-maximum-vessel-length-dimensio harbour-maximum-vessel-width-dimensio harbour-mean-tidal-current-rate harbour-passenger-handling-indicator-cod harbour-persistence-code harbour-pilotage-requirement-indicator-co harbour-prevailing-wind-direction-code harbour-prevailing-wind-maximum-quantit harbour-refuelling-availability-indicator-cod harbour-refuelling-location-text harbour-refuelling-type-code harbour-seasonal-detail-text harbour-tidal-mean-neap-range-dimension harbour-tidal-mean-spring-range-dimensio harbour-tidal-text harbour-transit-accommodation-indicatorharbour-vehicle-handling-type-code

contains / is-contained-by

NETWORK-SERVICE

provides / is-provided-by

network-id (FK) network-service-index

network-service-category-code network-service-subcategory-c

NETWORK-CAPACITY network-id (FK) network-capacity-index has / is-specified-for

network-capacity-bandwidth network-capacity-protocol-c

FACILITY-STATUS facility-status-id (FK) object-item-status-index (FK)

network-id (FK) network-frequency-index network-frequency-band-code network-frequency-discrete-frequency-quant network-frequency-band-lower-frequency-qu network-frequency-band-upper-frequency-qu network-frequency-effective-start-date network-frequency-effective-start-time network-frequency-effective-end-date network-frequency-effective-end-time network-frequency-modulation-code network-frequency-purpose-text

is-identified-by / identifies

feature-category-code

affiliation-geopolitical-code

government-organisation-type-id (FK)

AFFILIATION-RELIGION

government-organisation-type-category-co government-organisation-type-main-activity

person-id (FK) person-identification-document-index

affiliation-id (FK)

affiliation-religion-code

government-organisation-type-category-co

meteorologic-feature-id (FK)

control-feature-id (FK)

meteorologic-feature-category-code meteorologic-feature-interpretation-c meteorologic-feature-probability-frac meteorologic-feature-source-code

control-feature-category-co

military-organisation-type-id (FK)

has-for-support-a-specific / is-constituted-to-support

person-identification-document-code person-identification-document-numbe

METEOROLOGIC-FEATURE

CONTROL-FEATURE

MILITARY-ORGANISATION-TYPE

military-organisation-type-category military-organisation-type-service-c

PERSON-LANGUAGE-SKILL person-id (FK) person-language-skill-index

UNIT-TYPE

GEOGRAPHIC-FEATUR

‹

unit-type-id (FK)

unit-type-category-code unit-type-arm-category-code unit-type-arm-specialisation-code unit-type-supplementary-specialisation-code unit-type-general-mobility-code unit-type-qualifier-code unit-type-size-code unit-type-principal-equipment-type-id (FK) unit-type-supported-military-organisation-type

executive-military-organisation-type-id (FK) executive-military-organisation-type-catego

meteorologic-feature-category-cod

geographic-feature-id (F

ROUTE

route-id (FK)

route-direction-usage-c route-mobility-code

PRECIPITATION

LIGHT

precipitation-id (FK)

light-id (FK)

WIND

wind-id (FK) MILITARY-POST-TYPE military-post-type-id (FK)

EXECUTIVE-MILITARY-ORGANISATION-TY

person-language-skill-category-code person-language-skill-general-proficiency-c person-language-skill-listening-proficiency person-language-skill-reading-proficiency-l person-language-skill-speaking-proficiency person-language-skill-writing-proficiency-le

military-obstacle-category-co

HARBOUR-DRY-DOCK

harbour-id (FK) harbour-dry-dock-index

MINEFIELD

minefield-id (FK)

harbour-dry-dock-boat-lift-capacity-qua harbour-dry-dock-depth-dimension harbour-dry-dock-length-dimension harbour-dry-dock-location-text harbour-dry-dock-name harbour-dry-dock-width-dimension harbour-dry-dock-workshop-code

minefield-depth-placementminefield-mine-spacing-dim minefield-pattern-code minefield-persistence-code minefield-purpose-code minefield-stopping-power-c

contains / is-contained-by

military-post-type-category-c military-post-type-rank-code

light-category-code light-up-time light-down-time light-moon-phase-co

task-formation-type-id (FK) task-formation-type-category-co

FGAN

ICING

atmosphere-id (FK) atmosphere-humidity-fraction atmosphere-pressure-rate atmosphere-pressure-system-category-c atmosphere-temperature atmosphere-temperature-gradient-code

icing-category-code icing-severity-qualifier-

VISIBILITY

CLOUD-COVER

visibility-id (FK)

cloud-cover-id (FK)

visibility-category-co visibility-direction-co visibility-range-dime

cloud-cover-category-code cloud-cover-base-dimension cloud-cover-average-coverage-c cloud-cover-light-refraction-frac

contains / is-contained-by

harbour-id (FK) harbour-anchorage-index harbour-anchorage-bottom-type-code harbour-anchorage-day-limit-net-explosive-q harbour-anchorage-draught-high-tide-dimens harbour-anchorage-draught-low-tide-dimens harbour-anchorage-length-dimension harbour-anchorage-moorings-type-code harbour-anchorage-name harbour-anchorage-night-limit-net-explosiveharbour-anchorage-vessel-tonnage-quantity harbour-anchorage-width-dimension

contains / is-contained-by

HARBOUR-BERTH

harbour-id (FK) harbour-berth-index

contains / is-contained-by

HARBOUR-ANCHORAGE

icing-id (FK)

wind-category-code wind-direction-angle wind-speed-rate wind-nbc-yield-qualifier ATMOSPHERE

TASK-FORMATION-TYPE

precipitation-category-c precipitation-rate

harbour-berth-deadweight-tonnage-qu harbour-berth-depth-dimension harbour-berth-length-dimension harbour-berth-location-text harbour-berth-name

contains / is-contained-by HARBOUR-BASIN contains / is-contained-by

harbour-id (FK) harbour-basin-index harbour-basin-deadweight-tonnage-q harbour-basin-depth-dimension harbour-basin-length-dimension harbour-basin-location-text harbour-basin-name

HARBOUR-SLIPWAY

harbour-id (FK) harbour-slipway-index

harbour-slipway-gradient-an harbour-slipway-length-dim harbour-slipway-location-te harbour-slipway-name harbour-slipway-width-dime

operational-information-group-id (FK) organisation-id (FK) operational-information-group-organisation-association-index (FK) operational-information-group-organisation-association-status-index

uxo-status-exposure-code uxo-status-qualifier-code

harbour-id (FK) harbour-jetty-index

harbour-jetty-day-limit-net-explosive-quantity harbour-jetty-length-dimension harbour-jetty-maximum-deadweight-tonnage-q harbour-jetty-maximum-draught-dimension harbour-jetty-name harbour-jetty-night-limit-net-explosive-quantity harbour-jetty-rail-capacity-quantity harbour-jetty-rail-served-indicator-code harbour-jetty-vessel-maximum-beam-dimensio

identifies-the-beginning-of identifies-the-end-for

harbour-quay-container-handling-type-code harbour-quay-container-maximum-handling-lengthharbour-quay-container-maximum-handling-weightharbour-quay-crane-offloading-lift-quantity harbour-quay-crane-offloading-type-code harbour-quay-day-limit-net-explosive-quantity harbour-quay-draught-dimension harbour-quay-length-dimension harbour-quay-maximum-deadweight-tonnage-quan harbour-quay-name harbour-quay-night-limit-net-explosive-quantity harbour-quay-rail-capacity-quantity harbour-quay-rail-served-indicator-code harbour-quay-storage-code harbour-quay-vessel-maximum-beam-dimension

identifies-the-end-for identifies-the-beginning-of

identifies-the-end-for identifies-the-beginning-of

location-id location-category-co location-category-cod

POINT-REFERENCE coordinate-system-id (FK)

is-origin-for / is-defined-using is-endpoint-of-x-vector-for / is-defined-using is-endpoint-of-y-vector-for / is-defined-using

LINE line-id (FK

OBJECT-REFERENCE

geographic-feature-status-code geographic-feature-status-demolition-status-c geographic-feature-status-mine-presence-cod geographic-feature-status-recirculation-indicat geographic-feature-status-surface-condition-co geographic-feature-status-surface-firmness-co

coordinate-system-id (FK) object-reference-object-item-id (FK) object-reference-location-id (FK) object-reference-object-item-location-inde

P

used-for-expression-of / expressed-with-reference-to

line-point-sequence-qua line-point-point-id (FK)

geometric-volume-id (FK)

POINT is-used-as / makes-reference-to is-part-of-the-boundary-for

point-id (FK)

geometric-volume-category-code geometric-volume-lower-vertical-distance-i geometric-volume-upper-vertical-distance-i

point-category-co

geometric-volume-category-cod

is-the-centre-for / has-as-its-centre

CORRIDOR-AREA corridor-area-id (FK)

SPHERE-VOLUME

corridor-area-width-dimensio corridor-area-centre-line-id (

sphere-volume-id (FK) sphere-volume-radius-dimensio sphere-volume-centre-point-id (

medical-facility-status-interval-evacuation-destina medical-facility-status-interval-evacuation-quantit

POLYARC-AREA polyarc-area-id (FK)

is-the-vertex-for / has-as-its-vertex

polyarc-area-begin-bearing-angle polyarc-area-end-bearing-angle polyarc-area-arc-radius-dimension polyarc-area-defining-line-id (FK) polyarc-area-bearing-origin-point-i

CONE-VOLUME

medical-facility-status-facility-id (FK) begin-object-item-status-index (FK) end-object-item-status-index (FK) medical-facility-status-interval-casualty-type-index

cone-volume-id (FK) cone-volume-defining-surface-id cone-volume-vertex-point-id (FK

medical-facility-status-interval-casualty-type-code medical-facility-status-interval-casualty-type-arrival-qu medical-facility-status-interval-casualty-type-admitted

medical-facility-status-facility-id (FK) begin-object-item-status-index (FK) end-object-item-status-index (FK) medical-facility-status-interval-casualty-group-index medical-facility-status-interval-casualty-group-code medical-facility-status-interval-casualty-group-completed-surge medical-facility-status-interval-casualty-group-death-quantity

is-used-to-define / is-defined-using is-used-to-define / is-defined-using

bounds-on-the-top bounds-on-the-bottom

POLYGON-AREA

surface-volume-id (FK)

polygon-area-id (FK)

surface-volume-defining-surface-id

polygon-area-bounding-line-i

vertical-distance-id

ORBIT-AREA

point-category-code

vertical-distance-category-c vertical-distance-dimension vertical-distance-precision-

medical-facility-status-facility-id (FK) object-item-status-index (FK) medical-facility-status-casualty-evacuation-index

orbit-area-id (FK) orbit-area-alignment-code orbit-area-width-dimension orbit-area-first-point-id (FK) orbit-area-second-point-id (

is-second-point-for / is-defined-using FAN-AREA fan-area-id (FK)

has

medical-facility-status-casualty-evacuation-destinati medical-facility-status-casualty-evacuation-sitting-qu medical-facility-status-casualty-evacuation-stretcher

is-the-boundary-for / is-bounded-by

is-first-point-for / is-defined-using

VERTICAL-DISTANCE

has

MEDICAL-FACILITY-STATUS-CASUALTY-EVACUAT

surface-category-code

constitutes-the-set-of-waypoints-for / is-defined-using

is-used-to-define / has-as-its-bearing-origin

MEDICAL-FACILITY-STATUS-INTERVAL-EVACUA

MEDICAL-FACILITY-STATUS-INTERVAL-CASUALTY-GROUP has

surface-id (FK) surface-category-cod

line-id (FK) line-point-index

GEOMETRIC-VOLUME

CONTROL-FEATURE-STATUS

SURFACE

is-defined-using / is-used-in-the-definition-of

LINE-POINT

SURFACE-VOLUME

HARBOUR-QUAY

harbour-id (FK) harbour-quay-index

LOCATION coordinate-system-reference-category-co

MEDICAL-FACILITY-STATUS-INTERVAL-CASUALTY-T

medical-facility-status-surgery-backlog-d

HARBOUR-JETTY

coordinate-system-reference-category-c

medical-facility-status-facility-id (FK) begin-object-item-status-index (FK) end-object-item-status-index (FK) medical-facility-status-interval-evacuation-index

medical-facility-status-facility-id (FK) object-item-status-index (FK)

operational-information-group-organisation-association-status-category-code operational-information-group-organisation-association-status-effective-date operational-information-group-organisation-association-status-effective-time operational-information-group-organisation-association-status-establishing-org

coordinate-system-id

point-reference-origin-point-id (FK point-reference-x-vector-point-id (F point-reference-y-vector-point-id (F

geographic-feature-status-id (FK) object-item-status-index (FK)

control-feature-status-investigation-statuscontrol-feature-status-nbc-threat-level-code control-feature-status-security-status-code control-feature-status-usage-status-code

uxo-status-id (FK) object-item-status-index (

MEDICAL-FACILITY-STATUS

NATO ratification as STANAG 5525 control-feature-category-code

military-organisation-type-category-c

is-recognised-as-having / is-ascribed-to

PERSON-IDENTIFICATION-DOCUMEN

P

provides-geometric-definition-for

control-feature-status-id (FK) object-item-status-index (FK)

UXO-STATUS

facility-status-category-cod

„ Edition 3.0 published in December 2005 affiliation-id (FK)

GOVERNMENT-ORGANISATION-TYPE

materiel-status-category-cod

facility-status-category-code facility-status-demolition-status-code facility-status-mine-presence-code facility-status-occupation-program-indicato facility-status-operational-status-code facility-status-operational-status-qualifier-c facility-status-reserve-indicator-code facility-status-security-status-code facility-status-usage-status-code

has / is-ascribed-to

context-element-status-category-code context-element-status-effective-date context-element-status-effective-time context-element-status-establishing-organisatio

COORDINATE-SYSTEM

GEOGRAPHIC-FEATURE-STATUS

materiel-status-category-code materiel-status-demolition-status-code materiel-status-operational-status-code materiel-status-operational-status-qualifie materiel-status-operational-status-modemateriel-status-reserve-indicator-code materiel-status-safety-status-code materiel-status-usage-status-code

NETWORK-FREQUENCY

MILITARY-OBSTACLE HARBOUR

AFFILIATION-GEOPOLITICA

MATERIEL-STATUS

can-be-accessed-via / provides-access-to

network-id (FK)

provides-coordinate-frame-reference-for

context-id (FK) context-element-index (FK) context-element-status-index

object-item-location-accuracy-quanti object-item-location-bearing-angle object-item-location-bearing-accurac object-item-location-speed-rate object-item-location-speed-accuracy object-item-location-use-category-co reporting-data-id (FK)

OPERATIONAL-INFORMATION-GROUP-ORGANISATION-ASSOCIATION-STA

person-status-duty-status-code person-status-physical-status-code person-status-physical-status-qualifie person-status-radiation-dose-code person-status-reserve-indicator-code

address-id (FK)

NETWORK

affiliation-category-co

provides-applicable-information-for / is-referenced-to

organisation-status-operational-status-code organisation-status-operational-status-qualifie organisation-status-availability-code organisation-status-command-and-control-rol organisation-status-commitment-status-code organisation-status-fire-mode-code organisation-status-nbc-dress-state-code organisation-status-radiation-dose-code organisation-status-readiness-code organisation-status-readiness-duration organisation-status-reinforcement-code organisation-status-reserve-indicator-code organisation-status-usage-status-code

person-status-id (FK) object-item-status-index (FK)

PHYSICAL-ADDRESS ELECTRONIC-ADDRESS

CONTEXT-ELEMENT-STATUS

object-item-id (FK) location-id (FK) object-item-location-index

organisation-status-id (FK) object-item-status-index (FK) PERSON-STATUS

address-category-code

electronic-address-nam network-id (FK) network-service-index (

BRIDGE

affiliation-id

organisation-type-id (FK)

OPERATIONAL-INFORMATION-GROUP-ORGANISATION-ASS

ORGANISATION-STATUS

address-category-code address-place-name-te

airfield-id (FK)

object-type-establishment-object-type-detail-major-part-indic object-type-establishment-object-type-detail-quantity object-type-establishment-object-type-detail-object-type-id ( object-type-establishment-detail-object-type-establishment-

AFFILIATION

is-cited-by P

OBJECT-ITEM-LOCATION

object-item-status-category-code

address-id AIRFIELD

established-object-type-id (FK) object-type-establishment-index (FK) object-type-establishment-object-type-detail-index

is-ascribed-to

vessel-type-category-code vessel-type-subcategory-c

operational-information-group-category

operational-information-group-organisation-association-categor provides-applicable-information-for / is-referenced-to

object-item-status-category-code object-item-status-hostility-code object-item-status-booby-trap-indicatorobject-item-status-emission-control-cod reporting-data-id (FK)

is-reference-for ADDRESS facility-category-code

OBJECT-TYPE-ESTABLISHMENT-OBJECT-TYPE-DETAIL

vessel-type-id (FK)

operational-information-group-id (FK)

provides

operational-information-group-id (FK) organisation-id (FK) operational-information-group-organisation-association-index

„ Generic – not derived from any specific system VESSEL-TYPE

OPERATIONAL-INFORMATION-GROUP

reporting-data-absolute-timing-effective-start-d reporting-data-absolute-timing-effective-start-ti reporting-data-absolute-timing-effective-end-da reporting-data-absolute-timing-effective-end-tim provides-applicable-information-for / is-referenced-to

object-item-id (FK) object-item-status-index

object-item-id (FK) address-id (FK) object-item-address-index

facility-id (FK)

object-item-id (FK) established-object-type-id (FK) object-type-establishment-index (FK) object-item-object-type-establishment-index

is-specified-through identifies-establishment-for-detail-object-type-in / / is-a-component-of references

nuclear-agent-type-id (FK)

object-item-id (FK) affiliation-id (FK) object-item-affiliation-inde

OBJECT-ITEM-OBJECT-TYPE-ESTABLISHME is-assigned-through

nbc-equipment-type-category-c

VEHICLE-TYPE

Z

has / is-ascribed-to

REPORTING-DATA-ABSOLUTE-TIMING

OBJECT-ITEM-STATUS

FACILITY

OBJECT-ITEM-AFFILIATIO

convoy-day-speed-rate convoy-day-vehicle-gap-dime convoy-halt-duration convoy-night-speed-rate convoy-night-vehicle-gap-dim convoy-packet-gap-dimensio convoy-packet-size-quantity

established-object-type-id (FK) object-type-establishment-index

chemical-agent-type-id (FK)

miscellaneous-equipment-type-catego

nbc-equipment-type-id (FK)

context-assessment-text context-assessment-effective-da context-assessment-effective-tim context-assessing-organisation-i

reporting-data-relative-timing-offset-duration reporting-data-relative-timing-reference-action-task-i

establishes / is-established-by

OBJECT-ITEM-ADDRESS

convoy-id (FK)

OBJECT-TYPE-ESTABLISHMENT

CHEMICAL-AGENT-TYPE

miscellaneous-equipment-type-id (FK)

NBC-EQUIPMENT-TYPE

has-for-address / is-the-address-for

CONVOY

is-specified-as-part-of / references

BIOLOGICAL-AGENT-TYPE

context-id (FK) context-assessment-index

reporting-data-relative-timing-reporting-data-id (FK)

is-the-reporting-agent-for / is-reported-by

has / is-ascribed-to

unit-formal-abbreviated-nam

land-weapon-type-category-code land-weapon-type-subcategory-code land-weapon-type-calibre-text land-weapon-type-fire-guidance-indicat

CONTEXT-ASSESSMENT

establishes / is-established-by

is-assigned-establishment-through

unit-id (FK)

land-weapon-type-id (FK)

identifies-the-data-for

REPORTING-DATA-RELATIVE-TIMING

provides-applicable-information-for / is-referenced-to is-geometrically-defined-through

UNIT

engineering-equipment-type-category

LAND-WEAPON-TYPE

reference-id

has-a-role-with-respect-to organisation-category-cod

ammunition-type-category-c ammunition-type-calibre-tex

engineering-equipment-type-id (FK)

context-association-status-category-code context-association-status-effective-date context-association-status-effective-time context-association-status-establishing-organisat

reporting-data-id (FK

provides-applicable-information-for / is-referenced-to

has / is-ascribed-to P

context-association-subject-context-id (FK) context-association-object-context-id (FK) context-association-status-index

context-id (FK) context-element-ind

reporting-data-timing-category-cod

object-item-association-subject-object-item object-item-association-object-object-itemobject-item-association-index (FK) object-item-association-status-index

„ Semantic definitions & extensive business rules ammunition-type-id (FK)

context-association-category-code

CONTEXT-ASSOCIATION-STATUS CONTEXT-ELEMENT

reference-description-text reference-security-classification reference-source-text reference-transmittal-type-code

P object-item-association-status-category-co reporting-data-id (FK)

context-association-subject-context-i context-association-object-context-id

context-category-code

REFERENCE provides-information-related-to / is-amplified-by

CONTEXT-ASSOCIATION

is-the-object-of Z

has-as-constituent-part / is-a-part-of

is-cited-in / is-referenced-to

OBJECT-ITEM-ASSOCIATION-STATUS

provides-applicable-information-for / is-referenced-to

organisation-id (FK)

group-characteristic-age-group-code group-characteristic-disease-code group-characteristic-disease-transmissibility-ind group-characteristic-gender-code group-characteristic-language-code group-characteristic-triage-code

object-type-id (FK) affiliation-id (FK) object-type-affiliation-ind

AMMUNITION-TYPE

is-the-subject-of

context-category-code context-name context-security-classification

reporting-data-absolute-timing-reporting-data-i

group-characteristic-id

consumable-materiel-type-category-c

ENGINEERING-EQUIPMENT-TYPE

context-id

context-id (FK) reporting-data-id (FK) context-reporting-data-association-index

reporting-data-id (FK)

object-item-association-subject-object-item P object-item-association-object-object-itemhas / object-item-association-index (FK) is-ascribed-to

ORGANISATION

is-made-up-through / specifies-the-composition-of GROUP-CHARACTERISTIC

CONTEXT

context-reporting-data-association-category

establishes / is-established-by

assigns-lfril-code-in

electronic-equipment-type-category-co electronic-equipment-type-subcategor

provides-applicable-information-for / is-referenced-to

ORGANISATION-STRUCTURE

object-item-association-category-code object-item-association-subcategory-code action-task-id (FK)

context-object-item-association-status-category-code context-object-item-association-status-effective-date context-object-item-association-status-effective-time context-object-item-association-status-establishing-organis

is-the-subject-of

is-the-subject-of

is-the-object-of

reporting-data-accuracy-code reporting-data-category-code reporting-data-counting-indicator-code reporting-data-credibility-code reporting-data-reliability-code reporting-data-reporting-date reporting-data-reporting-time reporting-data-source-type-code reporting-data-timing-category-code reference-id (FK) reporting-data-reporting-organisation-id

provides-applicable-information-for / is-referenced-to

ORGANISATION-STRUCTURE-DETAIL

object-item-association-subject-object-item object-item-association-object-object-itemobject-item-association-index

object-item-category-code

provides-categorisation-for / is-classified-according-to has

reporting-data-id provides-applicable-information-for / is-referenced-to

is-specified-for / requires-the-use-of OBJECT-ITEM-ASSOCIATION

object-item-group-account-detail-quanti object-item-group-account-detail-qualifie group-characteristic-id (FK) person-type-id (FK)

consumable-materiel-type-category-code consumable-materiel-type-subcategory-code consumable-materiel-type-hazard-code consumable-materiel-type-issuing-element-code consumable-materiel-type-issuing-quantity consumable-materiel-type-issuing-unit-of-measu consumable-materiel-type-issuing-weight-quant consumable-materiel-type-perishability-indicato

context-id (FK) object-item-id (FK)

CONTEXT-REPORTING-DATA-ASSOCIATIO

reporting-data-id (FK

has-an-associated / is-associated-with

object-item-id (FK) object-item-group-account-index (FK) object-item-group-account-detail-index

consumable-materiel-type-id (FK)

is-part-of

REPORTING-DATA

holding-operational-qua holding-total-quantity reporting-data-id (FK)

object-item-id (FK) object-type-id (FK) object-item-type-ind

context-id (FK) object-item-id (FK) context-object-item-association-status-index

has / is-ascribed-to CONTEXT-OBJECT-ITEM-ASSOCIATION

context-object-item-association-categor

object-item-id (FK) object-type-id (FK) holding-index

OBJECT-ITEM-TYPE

is-the-reason-for / is-based-on

object-item-group-account-na action-id (FK) reporting-data-id (FK)

OBJECT-ITEM-GROUP-ACCOUNT-DETA

CONSUMABLE-MATERIEL-TYPE

equipment-type-category-code equipment-type-loaded-weight-qua equipment-type-unloaded-weight-q

request-id (FK) request-answer-index (F reporting-data-id (FK)

HOLDING

has / belongs-to

references / is-relevant-for

is-the-subject-of

object-item-id (FK) object-item-group-account-in

CONTEXT-OBJECT-ITEM-ASSOCIATION-STATUS

is-comprised-of

is-the-object-of

object-item-category-code object-item-name object-item-alternate-identification

candidate-target-detail-association-subject-candidate-target-list-i candidate-target-detail-association-subject-candidate-target-deta candidate-target-detail-association-object-candidate-target-list-id candidate-target-detail-association-object-candidate-target-detail candidate-target-detail-association-category-code

provides-applicable-information-for / is-referenced-to

REQUEST-ANSWER-ELE

request-answer-category-c reporting-data-id (FK)

object-item-id

is-the-owner-of

CANDIDATE-TARGET-DETAIL-ASSOCIATION

provides-circumstances-for

request-id (FK) request-answer-index results-in / is-a-response-to

request-category-code request-immediate-interest-indicator request-latest-answer-date request-latest-answer-time

OBJECT-ITEM-GROUP-ACCO

is-enumerated-in / is-part-of

organisation-materiel-type-association-assigned-land-forces-reportableorganisation-materiel-type-association-assigned-land-forces-reportableorganisation-materiel-type-association-assigned-land-forces-reportable-

object-type-id (FK)

candidate-target-list-id (FK) candidate-target-detail-index

request-id (FK)

is-the-object-of

organisation-id (FK) materiel-type-id (FK)

candidate-target-list-id (FK) candidate-target-detail-index

serves-as-timing-reference-for / uses-as-timing-reference

REQUEST

is-classified-as

is-cited-in / is-the-count-of

ORGANISATION-MATERIEL-TYPE-ASSOCIATION

CONTROL-FEATURE-TYPE

geographic-feature-type-id (FK) geographic-feature-type-category-c

rule-of-engagement-id

rule-of-engagement-name rule-of-engagement-descriptionowning-organisation-id (FK)

CANDIDATE-TARGET-DETAIL

action-context-category-co

OBJECT-ITEM

organisation-action-task-rule-of-engagement-status-category-co organisation-action-task-rule-of-engagement-status-effective-sta organisation-action-task-rule-of-engagement-status-effective-sta organisation-action-task-rule-of-engagement-status-effective-end organisation-action-task-rule-of-engagement-status-effective-end

materiel-type-category-code

GEOGRAPHIC-FEATURE-TYPE

RULE-OF-ENGAGEMENT

action-task-id (FK) rule-of-engagement-id (FK) organisation-action-task-rule-of-engagement-status-organisation organisation-action-task-rule-of-engagement-status-index

is-the-object-of

action-id (FK) context-id (FK) action-context-index

provides-applicable-information-for / is-referenced-to provides-applicable-information-for / is-referenced-to

object-item-id (FK)

is-authority-for-the-use-of / is-used-as-specified-by

ORGANISATION-ACTION-TASK-RULE-OF-ENGAGEMENT-STA

is-the-subject-of

ACTION-CONTEXT

establishes / is-established-by is-specified-in / records-the-observed-results-for is-specified-as / is-a-designation-for REQUEST-ANSWER

is-subject-of / is-constrained-to

is-used-as-a-classification-for

materiel-type-category-code materiel-type-reportable-item-text materiel-type-stock-number-text materiel-type-supply-class-code materiel-type-maximum-height-dime materiel-type-maximum-length-dime materiel-type-maximum-width-dime

candidate-target-detail-authorisation-approval candidate-target-detail-authorisation-priority-q reporting-data-id (FK)

candidate-target-detail-category-co

provides-applicable-information-for / is-referenced-to

is-specified-as / is-a-designation-for

is-a-constraint-on

person-type-category-code person-type-subcategory-c person-type-rank-code

candidate-target-list-id (FK) candidate-target-detail-index (FK) candidate-target-detail-authorisation-index

is-constrained-by

is-authority-for-the-use-of / is-used-as-specified-by

has

PERSON-TYPE

CANDIDATE-TARGET-DETAIL-AUTHORISATIO

identifies-the-source-for / is-referenced-to has / is-ascribed-to

action-effect-item-fractio object-item-id (FK)

is-assigned / is-the-approval-for

candidate-target-list-authorisation-indicator candidate-target-list-authorisation-priority-q reporting-data-id (FK)

identifies-the-source-for / is-referenced-to

action-id (FK) action-effect-index (FK)

action-effect-type-quanti object-type-id (FK)

action-task-status-category-code action-task-status-completion-fracti action-task-status-planning-indicato action-task-status-progress-code action-task-status-amend-timing-co reporting-data-id (FK)

candidate-target-list-id (FK) candidate-target-list-authorisation-index

action-context-status-category-code action-context-status-effective-date action-context-status-effective-time action-context-status-establishing-organisatio

CANDIDATE-TARGET-DETAIL

establishes / is-established-by

MATERIEL-TYPE

action-task-id (FK) action-task-status-index

CANDIDATE-TARGET-LIST-AUTHORISATIO

action-id (FK) context-id (FK) action-context-index (FK) action-context-status-index

ACTION-EFFECT-ITEM

action-id (FK) action-effect-index (FK)

ACTION-TASK-STATUS

may-be-specified-as / may-specify

action-task-id (FK) rule-of-engagement-id (FK)

object-type-category-code

ACTION-CONTEXT-STATUS

is-specified-in / records-the-observed-results-for

ACTION-TASK-RULE-OF-ENGAGE

person-type-id (FK)

facility-type-id (FK)

ACTION-EFFECT-TYPE

object-type-id

is-the-load-in / specifies-the-stored-amount-of

FACILITY-TYPE

action-effect-category-cod action-effect-description-c action-effect-severity-code reporting-data-id (FK)

provides-applicable-information-for / is-referenced-to

241 entities 1244 attributes 7592 fixed domain values

object-type-capability-norm-mission-prima object-type-capability-norm-quantity

bridge-type-id (FK)

nbc-event-category-code nbc-event-subcategory-code nbc-event-alarm-result-indicator-code nbc-event-confirmation-test-indicatornbc-event-dose-rate-quantity nbc-event-dose-rate-trend-code nbc-event-flash-to-bang-time nbc-event-release-code nbc-event-spill-size-code nbc-event-yield-group-code

candidate-target-list-id (FK) candidate-target-detail-index

may-be-specified-as / may-specify

OBJECT-TYPE

object-type-id (FK) capability-id (FK)

action-event-detail-classification-c action-event-detail-crime-indicator action-event-detail-text reporting-data-id (FK)

action-event-status-completion-frac reporting-data-id (FK)

nbc-event-id (FK)

is-specified-as / is-specification-of

OBJECT-TYPE-CAPABILITY-NORM

BRIDGE-TYPE

NBC-EVENT

action-task-category-code

is-specified-as / is-specification-of

action-event-id (FK) action-event-detail-index

action-effect-category-code

has / is-ascribed-to

has-its-role-specified-through

is-specified-with / is-specified-for

facility-type-category-cod

organisation-action-association-catego organisation-action-association-effecti organisation-action-association-effecti organisation-action-association-intent-

is-specified-as / is-specification-of

„ JC3IEDM 3.0 comprises surveillance-capability-id (FK)

is-indicated-by / is-indicator-of

ACTION-EVENT-STATUS

action-event-id (FK) action-event-status-index

action-task-category-code action-task-activity-code action-task-minimum-duration action-task-estimated-duration action-task-maximum-duration action-task-planned-start-date action-task-planned-start-time action-task-start-qualifier-code action-task-planned-end-date action-task-planned-end-time action-task-end-qualifier-code action-task-priority-code action-task-detail-text candidate-target-list-id (FK) organisation-structure-root-organisation-id organisation-structure-index (FK)

action-id (FK) action-objective-index (FK) action-objective-item-marking-index

TARGET

action-id (FK) action-resource-index (

mobility-capability-id (FK) mobility-capability-category-c mobility-capability-terrain-type

P

action-event-category-code

action-task-id (FK)

provides-applicable-information-for / is-referenced-to

action-id (FK) action-effect-index

candidate-target-detail-category-co candidate-target-detail-focus-typecandidate-target-detail-label-text candidate-target-detail-priority-qua candidate-target-detail-scheme-co

is-assigned / is-the-approval-for

identifies-the-source-for / is-referenced-to

ACTION-EFFECT

ACTION-EVENT-DETAIL

is-detailed-through has / is-ascribed-to

ACTION-TASK

action-objective-item-categorycandidate-target-list-id (FK) candidate-target-detail-index (F object-item-id (FK)

ACTION-OBJECTIVE-ITEM-MARKING ACTION-RESOURCE-ITE

MOBILITY-CAPABILITY

facility-type-category-co

action-event-id (FK)

ACTION-OBJECTIVE-ITEM

action-id (FK) action-objective-index (FK)

action-objective-item-category-co

mission-capability-category mission-capability-level-cod mission-capability-qualifier-

may-be-used-in-planning / planning-may-use

action-event-category-co

ACTION-OBJECTIVE-TYPE

MISSION-CAPABILITY

is-used-in-the-definition-of / is-defined-with

is-measured-by / records-observed-results-of

action-category-code

ACTION-RESOURCE-EMPLOYMENT

action-resource-employment-category-code action-resource-employment-azimuth-fire-angle Z action-resource-employment-method-of-contro action-objective-index (FK)

action-resource-category-cod

candidate-target-list-association-category-code

consists-of / makes-up

ACTION-EVENT

is-used-according-to / describes-use-of

engineering-capability-facility-heightengineering-capability-facility-lengthengineering-capability-facility-width-d facility-type-id (FK)

is-the-object-of

CANDIDATE-TARGET-DETAIL

is-focussed-on / is-focus-of

action-objective-category-co

object-item-capability-mission-prima object-item-capability-quantity reporting-data-id (FK)

ENGINEERING-CAPABILITY

candidate-target-list-association-subject-candidate-targetcandidate-target-list-association-object-candidate-target-li

is-the-subject-of

candidate-target-list-na reporting-data-id (FK)

is-placed-within

„ Entity-relationship model in IDEF1X notation action-resource-category-code action-resource-criticality-indicator-code action-resource-qualifier-code action-resource-authorising-organisation

OBJECT-ITEM-CAPABILITY

FIRE-CAPABILITY

CANDIDATE-TARGET-LIST-ASSOCIATION

candidate-target-list-id

action-temporal-association-category-code action-temporal-association-reference-dura

action-functional-association-category-cod

action-objective-category-code action-objective-qualifier-code action-objective-priority-code action-objective-authorising-organisatio

is-the-subject-of / is-relevant-for

action-temporal-association-subject-action action-temporal-association-object-actionaction-temporal-association-index

ACTION-FUNCTIONAL-ASSOCIATION is-the-subject-of is-the-object-of

action-id (FK) action-objective-index

ACTION-RESOURCE

capability-category-cod

ACTION-TEMPORAL-ASSOCIATION

is-the-object-of is-the-subject-of

action-id

ACTION-OBJECTIVE

RELATIVE-POINT

MEDICAL-FACILITY-STATUS-PENDING-SU medical-facility-status-facility-id (FK) object-item-status-index (FK) medical-facility-status-pending-surgery-inde medical-facility-status-pending-surgery-tria medical-facility-status-pending-surgery-qua

ABSOLUTE-POINT is-specified-for

absolute-point-id (FK) absolute-point-latitude-coordinate absolute-point-longitude-coordina absolute-point-angular-precisionabsolute-point-vertical-distance-i

relative-point-id (FK) relative-point-x-coordinate-dimen relative-point-y-coordinate-dimen relative-point-z-coordinate-dimen relative-point-horizontal-precisio relative-point-vertical-precision-c coordinate-system-id (FK)

is-the-vertex-for / is-defined-using

fan-area-minimum-range-dimens fan-area-maximum-range-dimen fan-area-orientation-angle fan-area-sector-size-angle fan-area-vertex-point-id (FK)

TRACK-AREA track-area-id (FK)

is-beginning-point-for / is-defined-using is-ending-point-for / is-defined-using

track-area-left-width-dimens track-area-right-width-dimen track-area-begin-point-id (FK track-area-end-point-id (FK)

MEDICAL-FACILITY-STATUS-CASUALTY-BED-OC medical-facility-status-facility-id (FK) object-item-status-index (FK) medical-facility-status-casualty-bed-occupancy-in medical-facility-status-casualty-bed-occupancy-g medical-facility-status-casualty-bed-occupancy-q

Research Institute for Communication, Information Processing and Ergonomics

is-the-centre-for / has-as-its-centre is-the-first-conjugate-point-for / has-as-its-first-conjugate-point is-the-second-conjugate-point-for / has-as-its-second-conjugate-point

ELLIPSE ellipse-id (FK) ellipse-centre-point-id (FK) ellipse-first-conjugate-diameter-point-id ellipse-second-conjugate-diameter-poin

KIE

MIP JC3IEDM – Modeling Capabilities (1) OBJECT-TYPE

object-item-category-code

object-type-category-code

FACILITY-TYPE

PERSON-TYPE

FEATURE-TYPE

MATERIEL-TYPE

facility-type-category-code AIRFIELD-TYPE

materiel-type-category-code

feature-type-category-code

CONSUMABLE-MATERIEL-TYPE

FACILITY

ANCHORAGE

DRY-DOCK

GEOGRAPHIC-FEATURE-TYPE

GROUP-ORGANISATION-TYPE

CHEMICAL-MATERIEL-TYPE RADIOACTIVE-MATERIEL-TYPE

government-organisation-type-category-code

military-organisation-type-category-code UNIT-TYPE MILITARY-POST-TYPE TASK-FORMATION-TYPE

RAILWAY

JETTY

control-feature-category-code AIRSPACE-CONTROL-MEANS

ROAD

RUNWAY

APPROACH-DIRECTION SLIPWAY

NETWORK-SERVICE

equipment-type-category-code

CBRN-EQUIPMENT-TYPE ELECTRONIC-EQUIPMENT-TYPE ENGINEERING-EQUIPMENT-TYPE MISCELLANEOUS-EQUIPMENT-TYPE

NETWORK-FREQUENCY MILITARY-OBSTACLE

ROUTE-SEGMENT route-segment-category-code

VESSEL-TYPE

ROUTE

AIR-ROUTE-SEGMENT

GEOGRAPHIC-FEATURE METEOROLOGIC-FEATURE meteorologic-feature-category-code

military-obstacle-category-code

ATMOSPHERE ICING

MINEFIELD minefield-category-code

CLOUD-COVER LIGHT PRECIPITATION

RAILCAR-TYPE

WEAPON-TYPE

FGAN

feature-category-code

NETWORK-CAPACITY

VEHICLE-TYPE EXECUTIVE-MILITARY-ORGANISATION-TYPE

PERSON-LANGUAGE-SKILL PERSON-IDENTIFICATION-DOCUMENT

CONTROL-FEATURE

EQUIPMENT-TYPE

AIRCRAFT-TYPE MILITARY-ORGANISATION-TYPE

APRON

NETWORK

PRIVATE-SECTOR-ORGANISATION-TYPE GOVERNMENT-ORGANISATION-TYPE

CONVOY

QUAY

HARBOUR

BIOLOGICAL-MATERIEL-TYPE CIVILIAN-POST-TYPE

PERSON

UNIT

consumable-materiel-type-category-code AMMUNITION-TYPE

ORGANISATION

organisation-category-code

BRIDGE

BERTH

ROUTE-TYPE

organisation-type-category-code

FEATURE

BASIN

AIRFIELD

CONTROL-FEATURE-TYPE control-feature-type-category-code

MILITARY-OBSTACLE-TYPE

MATERIEL

facility-category-code

BRIDGE-TYPE

ORGANISATION-TYPE

OBJECT-ITEM-ALIAS

OBJECT-ITEM

MINEFIELD-LAND

MINEFIELD-MARITIME

VISIBILITY WIND

MINEFIELD-MARITIME-CASUALTY-ESTIMATE MINEFIELD-MARITIME-SUSTAINED-THREAT-MEASURE-OF-EFFECTIVENESS

Research Institute for Communication, Information Processing and Ergonomics

KIE

MIP JC3IEDM – Modeling Capabilities (2) Militarily relevant objects ‹ Current status and location ‹ Nominal/actual capabilities & equipment ‹ Geopolitical, ethnic, religious, and functional affiliations ‹ ORBAT & task organization ‹ Addresses „ Locations/Geometry ‹ Points, lines, surfaces, volumes ‹ Relative vs. absolute locations „

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

MIP JC3IEDM – Modeling Capabilities (3) Actions ‹ Temporal and functional relationships ‹ Rules of engagement ‹ Targets „ … „ Meta information ‹ Reporting organization ‹ Reporting date & time ‹ Accuracy, credibility, reliability ‹ Duration of validity ‹ etc. „

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

MIP JC3IEDM – XML Use Cases „

Data Exchange ‹ Web Services (e.g., exchange of business objects) ‹ Exchange with non-MIP databases ‹ MIP XML Exchange Mechanism

„

Transformation Services ‹ Supporting tactical communications interfaces, ADatP-3 or USMTF (effectively always lossy) ‹ Mediation between different versions of the MIP IEDM ‹ Export to various output/presentation formats, e.g., STANAG 5500-conformant messages or HTML

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Reference MIP XML Schema Definitions „

Reference MIP XML schema definitions ‹ MIP IEDM defines the C2 XML namespace semantics ‹ Avoid diversity of XML vocabularies ‹ Collaborative efforts ease national development, improve interoperability, and reduce national costs

„

Two reference XSDs for different purposes ‹ RDBMS XSD – Used for database replication ‹ WS/OO XSD – Used for web services/SOAs

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO XSD – Requirements (1) „ Message exchange ‹ ¨ ¨ ¨ ¨

Referentially complete, self-contained messages Ensure referential integrity within a single XML document Describe cyclic data structures Allow tailoring to specific business object XSDs No fragmentation of data to enhance readability

„ Replication & Query-based communication ‹ ‹ ¨ ¨

Initial synchronization, incremental updates Incomplete query results may refer to unknown objects Support references to external information Relax referential integrity checks (to be ensured by web service & client)

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO XSD – Requirements (2) „

Consider Naming and Design Rules (NDRs) ‹ Naming of XML elements & attributes, schema versioning, modularization, namespaces, (restricted) use of XML Schema constructs, etc. ¨ Discovery and reuse of common data elements

„

NATO Guidelines for XML Naming and Design (GXND) • Based on ISO/IEC 11179 (Metadata registry) and ISO 15000-5 (ebXML)

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO XSD – Design Principles „ Object-Oriented ‹ ‹ ‹

Structure of instance XML documents matches the natural OO concepts (e.g., inheritance, object identifiers, navigability) Abstraction from the technical aspects of the relational model Abstraction from any underlying persistence mechanism

„ Based on Syntactic Transformations only ‹ ‹ ‹ ‹

Suitable for any version of the MIP IEDM Transformations are easily traceable XSD can be generated automatically from the IDEF1X model Minimizes XSD maintenance cost

„ Checks Semantic Constraints ‹ ‹

Domain values, optionality, cardinality of relationships Type-safe document consistency

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO XSD – Transformation Rules Names ‹ Simple types, codes, attributes, entities „ Domains ‹ Simple types and codes ‹ Based on predefined XML Schema simple types „ Entities ‹ Optional and mandatory attributes ‹ Object identifiers replace JC3IEDM’s synthetic keys „ Relationships ‹ One-to-many relationships ‹ Sub-type relationships ‹ Many-to-many relationships (associative entities) „

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Transformation Rules – Identifying Relationships

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Transformation Rules – Subtype Relationships

Drop category codes

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Transformation Rules – Incomplete Subtyping MILITARY-ORGANISATION-TYPE military-organisation-type-id (FK) military-organisation-type-category-code military-organisation-type-service-code

military-organisation-type-category-code

AbstractMilitaryOrganisationType

abstract=“true” oid service-code

TASK-FORMATION-TYPE task-formation-type-id (FK)

MILITARY-POST-TYPE

task-formation-type-category-code

military-post-type-id (FK)

derived by extension

military-post-type-category-code military-post-type-rank-code UNIT-TYPE unit-type-id (FK) unit-type-category-code unit-type-arm-category-code unit-type-arm-specialisation-code unit-type-supplementary-specialisation-code unit-type-general-mobility-code unit-type-qualifier-code unit-type-size-code unit-type-principal-equipment-type-id (FK)

EXECUTIVE-MILITARY-ORGANISATION-TYPE executive-military-organisation-type-id (FK) executive-military-organisation-type-category-code

TaskFormationType

MilitaryPostType

(Other)MilitaryOrganisationType

abstract=“false” category-code

FGAN

UnitType

ExecutiveMilitaryOrgType

Research Institute for Communication, Information Processing and Ergonomics

KIE

Transformation Rules – Associative Entities

Object-to-Association Reasoning

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO Example – Description „ The White Horse Bridge across the Yukon River initially serves as a

passage between two minefields located on the north side of the river, one on each side of the bridge. The contingency plan is to use the bridge as part of an obstacle. If the units of the joint task force that are now deployed on the north side of the river need to withdraw, the bridge will be demolished to become part of the main obstacle. Source: JC3IEDM 3.0 Main Document

N

Obstacle Alpha

West Minefield

White Horse Bridge

East Minefield

Yukon River

S

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO Example – JC3IEDM Modeling LandMineField : ObjectType

IronHorse : BridgeTyoe

CompoundObstacle : MilitaryObstacleType

OID = OT1

OID = OT3

OID = OT4

: ObjectItemType

: ReportingData

: ObjectItemType

: ObjectItemType

: ObjectItemType

OID = RPTD001

West Minefield : MinefieldLand

East Minefield : MinefieldLand

White Horse Bridge : Bridge

Obstacle Alpha : MilitaryObstacle

OID = OI1

OID = OI2

OID = OI3

OID = OI4

: FacilityStatus

: ReportingDataAbsoluteTiming OID = 701

: FacilityStatus

: ReportingDataAbsoluteTiming OID = 702

: FacilityStatus

: FacilityStatus

: ReportingData OID = RPTD704

: FacilityStatus

: FacilityStatus

: ReportingDataAbsoluteTiming

: ReportingData

OID = RPTD705

OID = RPTD703

: ObjectItemAssociation OID = OIA1

: ObjectItemAssociationStatus : ObjectItemAssociation OID = OIA2

: ReportingDataAbsoluteTiming

: ObjectItemAssociation OID = OIA4

OID = RPTD005 : ObjectItemAssociationStatus Intelligence : Unit

1 CA Bde : Unit

OID = OI5

OID = OI6

: ObjectItemType

: ObjectItemAssociationStatus

: ObjectItemAssociationStatus

: ObjectItemAssociationStatus

: ObjectItemType

Intelligence : UnitType

CA Brigade : UnitType

OID = OT5

OID = OT6

FGAN

: ObjectItemAssociationStatus

: ReportingData OID = 711

: ReportingDataAbsoluteTiming OID = 712

Research Institute for Communication, Information Processing and Ergonomics

KIE

XML Document – Top-Level Structure OI1 West Minefield … … OI3 White Horse Bridge … OI4 Obstacle Alpha … ... Object Identifiers (OIDs) for referable entities RPTD705 … • Independent entities … • Elements that can be further specified

(e.g., associations with statuses)

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

XML Document – Entities OI1 West Minefield … 300 105 10 MIXED NUISNC REGTHK REMOTE MEDIUM OI3 White Horse Bridge 200 10 40 • Inheritance of attributes 5 RLWYVH • Domain value checks (including NULL)

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

XML Document – Bridge With Status Information OI3 White Horse Bridge … FR RPTD704 … 20031103171000.000 … PRPEXE … FR RPTD705 EXECTD • Relationships by nesting … • Cardinality/Optionality checks • Type-safe referential integrity … checks

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

XML Document – Status Update Reference to existing bridge OI3 FR RPTD704 REP RPTFCT 20031103171000.000 OI6 OIASST TIMNA PRPEXE NO OPR PASABL NOS

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Tool Support – Automatic Generation has-relevant-inf ormat ion-in

JC3IEDM Edition 0.80 9 September

CAP ABILI TY cap abil ity-id

ACT ION-REQUI RE D-CAPABI LITY actio n-id (FK) capa bil ity-id (FK)

is-quantif ied-in / quant if ie s

cap abil ity-categ ory-code cap abil ity-subc ategory-co de cap abil ity-day-n ight-cod e cap abil ity-uni t-o f-measu re -c ode

ACTION-RES OURCE ac ti on-id (FK) ac ti on-resou rce-ind ex

is-used-according-t o / describes-use-of

ACT ION-RESOURCE-TYPE acti on-id (FK) acti on-resource -i ndex (FK)

M OBI LITY-CAPAB ILITY mobi lity-ca pabil ity-id (FK)

Data model in ERwin XML format

ACTION-T EMPORAL-AS SOCI ATION ac ti on-tempo ra l-asso ciati on-subj ect-actio n-id (FK ) ac ti on-tempo ra l-asso ciati on-obj ect-action -i d (FK) ac ti on-tempo ra l-asso ciati on-ind ex

is-the-object -of is-t he-subject -of

is-indicated-by / is-indicator-of

a ction-ob jecti ve-item-ca te gory-cod e TA RGET

ACTI ON-OB JECTIV E-ITEM-MA RKI NG a ction-i d (FK) a ction-ob jecti ve-in dex (FK ) a ction-ob jecti ve-item-marki ng-in dex

action -i d (FK) action -o bjec ti ve-in dex (FK) ta rg et-engag ement-authori ty -c ode ta rg et-identi fie r-tex t ta rg et-vici nity-du ra ti on

is-ascribed-t o

is-the-user-of / is-used-by

ac ti on-id (FK) ac ti on-obj ective-inde x (FK)

is-specif icat ion-of

radioactive-event-category-code

facility-type-category-code

ca ndid ate-ta rg et-list-id (FK) ca ndid ate-ta rg et-detail -index (FK)

F EATURE-TYPE fea tu re -typ e-id (FK)

is-const rained-t o

EQUIPMENT-TY PE e quip ment-ty pe-id (FK) e quip ment-ty pe-catego ry-code e quip ment-ty pe-loa ded-wei ght-quan ti ty e quip ment-ty pe-unl oaded -w eigh t-qu antity e quip ment-ty pe-maxi mum-hei ght-dimen sion e quip ment-ty pe-maxi mum-len gth-dimen sion e quip ment-ty pe-maxi mum-width-di mensi on e quip ment-ty pe-fue l-capa city-qua ntity

provides-applicable-inf ormat ion-f or / is-ref erenced-to

consumable-materiel-type-category-code

is-the-subject -of

is-cit ed-in / is-the-count -of

OBJECT-IT EM-ALIAS o bjec t-i te m-i d (FK) o bjec t-i te m-a lia s-inde x

is-ref erenced-t o

AI RCRAFT-TYP E

organi sation -s truc tu re -ro ot-o rg anis ation-i d (FK) organi sation -s truc tu re -index

establishes /

is-assigned-establishment -t hrough

u nit-formal -abbreviated-na me-te xt u nit-ide ntifi cation -te xt

has

OB JECT-ITE M-OBJECT -T YPE-ES TABLISHMENT obj ect-item-id (FK) estab lis hed-obj ect-type-id (FK) obj ect-type-estab lis hment-ind ex (FK ) obj ect-item-obj ect-type-es ta bli shment-in dex

re porting -d ata-id (FK )

ge ograph ic-fea ture-soli d-surfa ce-compo sitio n-code ge ograph ic-fea ture-surfac e-category-co de ge ograph ic-fea ture-te rrai n-code ge ograph ic-fea ture-vegetati on-cod e CONTROL-FEA TURE con tro l-fea tu re -i d (FK)

AFF ILIATI ON-RELIGION affi lia ti on-id (FK)

is-ident if ie d-by /

is-recognised-as-having / is-ascribed-t o

identif ies

P ERSON-IDENTIF ICATION-DOCUMENT person -i d (FK) person -i denti fic ation-do cument-in dex

affili ation-ge opol itica l-code

person -i denti fic ation-do cument-cod e person -i denti fic ation-do cument-numb er-te xt

con tro l-fea tu re -c ategory-cod e

affi lia ti on-reli gio n-code

surfac e-vess el-type-i d (FK) ORGANIS ATION-T YPE o rg anis ation-typ e-id (FK ) o rg anis ation-typ e-category-co de o rg anis ation-typ e-command -functi on-ind icator-cod e o rg anis ation-typ e-command -a nd-control -category-co de o rg anis ation-typ e-descri ption-text

meteorol ogic -feature-categ ory-code meteorol ogic -feature-in te rp re tation-co de meteorol ogic -feature-proba bil ity-ratio meteorol ogic -feature-sou rc e-code meteorolo gic-feature-categ ory-code

ci vil ian-po st-ty pe-catego ry -c ode

government-organisation-type-category-code

PRIV ATE-SECTOR-ORGA NI SATI ON-TYPE p ri vate-se ctor-o rg anis ation-type -id (FK ) p ri vate-se ctor-o rg anis ation-type -category-co de p ri vate-se ctor-o rg anis ation-type -main-ac ti vity-co de

mili tary-organi sation -ty pe-catego ry -c ode mili tary-organi sation -ty pe-servi ce-code UNIT-TY PE has-f or-support-a-specif ic /

exec utive -mi li ta ry -o rg anis ation-type -c ategory-co de

is-the-ob ject-of

i s-the-subj ect-of ROUTE-SEGMENT route-se gment-id (FK)

clo ud-cover-c ategory-co de clo ud-cover-b ase-di mensi on clo ud-cover-top -dimen sion clo ud-cover-a verage -c overag e-code clo ud-cover-l igh t-refra ction-rati o ICING ici ng-id (FK) ici ng-cate gory-code ici ng-severity-qua lifier-cod e PRECI PIT ATION preci pitati on-id (FK) preci pitati on-catego ry-code preci pitati on-rate WI ND wind-i d (FK) wind-ca te gory-cod e wind-ai r-s tabil ity-categ ory-code wind-al titude-l ayer-cod e wind-di rection -a ngle wind-effec ti ve-do wnwin d-directi on-angl e wind-sp eed-rate wind-nu clea r-yi eld -q uali fi er-c ode

pe rs on-lan guage -s kil l-catego ry -code pe rs on-lan guage -s kil l-gene ra l-profi cie ncy-cod e pe rs on-lan guage -s kil l-li stenin g-profi cien cy-level-cod e pe rs on-lan guage -s kil l-readi ng-profi cie ncy-le vel-co de pe rs on-lan guage -s kil l-spea king -p ro fic ienc y-leve l-code pe rs on-lan guage -s kil l-writin g-profi cien cy-level-cod e

ai rspace -c ontrol-mea ns-tra nsit-in stru ction-tex t

CLOUD-COVE R clo ud-cover-i d (FK)

uni t-type -i d (FK) uni t-type -c ategory-co de uni t-type -a rm -c ategory-cod e uni t-type -a rm -s peci alis ation-co de uni t-type -s uppl ementary-sp ecia lisa ti on-cod e uni t-type -g eneral -m obil ity-code uni t-type -q uali fi er-c ode uni t-type -s ize-co de uni t-type -p ri nci pal-eq uipme nt-ty pe-id (FK) uni t-type -s upported -mi lita ry -o rg anis ation-type -i d (FK) EXECUTIVE-MI LITARY-ORGANISA TION-T YPE exec utive -mi li ta ry -o rg anis ation-type -i d (FK)

route-di re ction-us age-cod e route-mobi li ty -c ode route-mode -o f-transpo rtati on-code

atmosphe re -humid ity-ratio atmosphe re -inve rs ion-l ayer-code atmosphe re -pressure-rate atmosphe re -pressure-sy stem-catego ry -c ode atmosphe re -te mperature atmosphe re -te mperature-gradi ent-code

CI VILIA N-POST-TY PE ci vil ian-po st-ty pe-id (FK)

group-organ isati on-type-id (FK)

ROUTE route-id (FK)

AIRSP ACE -CONT ROL-M EANS ai rspace -c ontrol-mea ns-id (FK)

A TMOSPHERE atmosphe re -id (FK ) organisation-type-category-code

PERSON-LANGUAGE-SK ILL pe rs on-id (FK) pe rs on-lan guage -s kil l-ind ex

control-feature-categ ory-code

M ETEOROLOGI C-FEA TURE meteorol ogic -feature-id (FK)

route-se gment-catego ry-code route-se gment-mobi lity-co de route-se gment-mode-o f-tra nsportatio n-code

LIGHT l ight-id (FK) l ight-categ ory-code l ight-up-da te ti me l ight-down -d atetime l ight-moon -p hase-co de VI SIB ILITY visi bil ity-id (FK) visi bil ity-categ ory-code visi bil ity-di re ction-co de visi bil ity-range -d imens ion

route-segment-category-code

AIR-ROUTE-SEGMENT air-route-se gment-id (FK) air-route-se gment-requi re d-navi gatio n-performan ce-code air-route-se gment-civil-mi litary-c ode air-route-se gment-interna tional -route-code air-route-se gment-main ta ined -s peed-rate air-route-se gment-desc ri ption -te xt

RUNWA Y ru nway-i d (FK) ru nway-l ighti ng-presen ce-ind icator-cod e ru nway-wei ght-bea ri ng-cap acity-rate ru nway-pa vement-cl assi fic ation-nu mber-coun t ru nway-pa vement-type -c ode ru nway-pa vement-su bgrade-ca te gory-code ru nway-pa vement-max imum-tyre-press ure-code ru nway-pa vement-evalua ti on-method -code

ha rbour-airpo rt-nea r-i ndic ator-code ha rbour-approa ch-chan nel-de pth-dimen sion ha rbour-bio logi call y-secu re -avai labi lity-i ndic ator-code ha rbour-convoy-marsha lli ng-ind icator-co de ha rbour-day-l imit-net-exp losi ve-qu antity ha rbour-nig ht-l imi t-ne t-ex plos ive-q uantity ha rbour-dega ussi ng-ind icator-cod e ha rbour-dirty-bal las t-i ndic ator-c ode ha rbour-entrance -res tri ction s-ice-i ndica tor-c ode ha rbour-entrance -res tri ction s-swell -indi cator-code ha rbour-entrance -res tri ction s-te xt ha rbour-estima te d-ti me-of-a rri val-i ndic ator-c ode ha rbour-fi re -figh ti ng-cap abil ity-cod e ha rbour-fi re -figh ti ng-in dicato r-co de ha rbour-fi rs t-po rt-of-e ntry-indi cator-code ha rbour-fresh -w ater-a vail abi lity-i ndic ator-c ode ha rbour-las h-indi cator-code ha rbour-li ghterage-avail abil ity-in dica to r-co de ha rbour-maxi mum-vess el-draug ht-d imens ion ha rbour-maxi mum-vess el-le ngth-dime nsio n ha rbour-maxi mum-vess el-wid th -d imens ion ha rbour-mean-tid al-current-rate ha rbour-pass enger-han dli ng-ind icator-cod e ha rbour-persi stence-co de ha rbour-overhe ad-li mits-ind icator-co de ha rbour-pil otage-avail abil ity-in dica to r-co de ha rbour-pil otage-requ irement-in dica to r-c ode ha rbour-prevai li ng-win d-directi on-code ha rbour-prevai li ng-win d-maximu m-s peed-co de ha rbour-prevai li ng-win d-maximu m-s peed-rate ha rbour-refue lli ng-ava ila bili ty-indi cator-cod e ha rbour-refue lli ng-loc ation-tex t ha rbour-refue lli ng-type-co de ha rbour-seas onal -d etail -tex t ha rbour-shel ter-q uali ty-code ha rbour-tanker-fa cil ities -i ndi cator-code ha rbour-tidal -mean-nea p-ra nge-di mensi on ha rbour-tidal -mean-spri ng-range-d imens ion ha rbour-tidal -te xt ha rbour-tra nsit-acc ommoda ti on-in dicato r-co de ha rbour-tug-ava ilab ili ty-indi cator-code ha rbour-turning -a re a-indi cator-cod e ha rbour-vehi cle -h andl ing-type -c ode QUAY qua y-id (FK ) qua y-contai ner-handl ing -typ e-code qua y-contai ner-maximu m-handl ing-l ength-di mensi on qua y-contai ner-maximu m-handl ing-we ight-qua ntity qua y-crane-offlo adin g-lift-q uantity qua y-crane-offlo adin g-ty pe-code qua y-day-li mit-net-expl osi ve-qua ntity qua y-draught-di mensi on qua y-leng th -d imens ion qua y-maximu m-d eadwe ight-tonna ge-quan tity qua y-nigh t-l imit-net-exp losi ve-qu antity qua y-ra il-ca paci ty -c ount qua y-ra il-se rved-in dicato r-co de qua y-storage-cod e qua y-vesse l-maxi mum-beam-di mensi on

is-ascribed-to

NETWORK-SERVICE-STA TUS network-id (FK) network-servi ce-in dex (FK) network-servi ce-status -i ndex

j etty-day-li mit-net-expl osi ve-qua ntity j etty-leng th -d imens ion j etty-maximu m-d eadwe ight-tonna ge-quan tity j etty-maximu m-d raught-di mensi on j etty-nigh t-l imit-net-exp losi ve-qu antity j etty-ra il-ca paci ty -c ount j etty-ra il-se rved-in dicato r-co de j etty-vesse l-maxi mum-beam-di mensi on

l iqu id-surface-status-se a-state-code l iqu id-surface-status-su rface-co nditi on-code l iqu id-surface-status-wa ve-direc tion-co de

facil ity-status -c ategory-cod e facil ity-status -d emoli tion-status -c ode facil ity-status -e nemy-acti vity-co nditi on-code facil ity-status -mi ne-prese nce-cod e facil ity-status -o ccupa ti on-program-i ndic ator-code facil ity-status -o peration al-status-co de facil ity-status -o peration al-status-qu ali fie r-co de facil ity-status -res erve-in dicato r-co de facil ity-status -s ecurity-status -code facil ity-status -u sage-status -c ode

OBJECT-REFERENCE rel ative -coordi nate-system-i d (FK)

includes-report -of / report -is-part -of

MEDICAL-FACILITY -STATUS-INTERVAL-CASUALTY-GROUP me dical -faci li ty -s ta tu s-faci li ty -i d (FK) ob ject-ite m-s ta tu s-inde x (FK) me dical -faci li ty -s ta tu s-interva l-casu alty-group -index me dical -faci li ty -s ta tu s-interva l-casu alty-group -code me dical -faci li ty -s ta tu s-interva l-casu alty-group -compl eted-surgery-co unt me dical -faci li ty -s ta tu s-interva l-casu alty-group -death-cou nt

h as

mi nefi eld -ma ri time-de pth-plac ement-code mi nefi eld -ma ri time-ex pected-ve ssel -tran sit-coun t mi nefi eld -ma ri time-fu nction -code mi nefi eld -ma ri time-mmoe -i niti al-threat-probab ili ty-ra tio

has

MEDICAL-FACILITY -STATUS-PENDING-CASUALTY-EV ACUATI ON me dical -faci li ty -s ta tu s-faci li ty -i d (FK) ob ject-ite m-s ta tu s-inde x (FK) me dical -faci li ty -s ta tu s-pend ing-ca sualty -e vacua ti on-in dex me dical -faci li ty -s ta tu s-pend ing-ca sualty -e vacua ti on-des ti natio n-code me dical -faci li ty -s ta tu s-pend ing-ca sualty -e vacua ti on-si tti ng-coun t me dical -faci li ty -s ta tu s-pend ing-ca sualty -e vacua ti on-stretche r-co unt

MINEFIE LD-MARITI ME-SUSTAI NE D-THREAT-MEA SURE-OF-EFFE CTI VENESS mine fie ld-mariti me-id (FK ) mine fie ld-mariti me-sustai ned-threat-meas ure-of-effecti venes s-inde x mine fie ld-mariti me-sustai ned-threat-meas ure-of-effecti venes s-plan ned-du ra ti on mine fie ld-mariti me-sustai ned-threat-meas ure-of-effecti venes s-probab ili ty -ra ti o

CORRIDOR-AREA co rri dor-area-id (FK) co rri dor-area-wi dth-dimen sion co rri dor-area-cen tre-l ine-i d (FK)

P OLYARC-ARE A poly arc-area-id (FK)

is-the-vertex-f or /

poly arc-area-beg in-bea ri ng-ang le poly arc-area-end -b earing -a ngle poly arc-area-arc-radi us-dime nsio n poly arc-area-defini ng-li ne-id (FK) poly arc-area-bea ri ng-orig in-poi nt-id (FK )

cone -volume -defi ning -s urface -i d (FK) cone -volume -vertex-poi nt-id (FK )

is-used-to-def ine / is-def in ed-using is-used-to-def ine / is-def ined-usin g

uxo -status-expo sure-code uxo -status-qual ifier-code

POLYGON-ARE A po lygo n-area-id (FK)

SURFA CE-VOLUME surface-vol ume-id (FK) bounds-on-the-top

is-the-boundary-f or / is-bounded-by

po lygo n-area-boun ding -l ine -i d (FK)

surface-vol ume-de fini ng-surface-id (FK)

bounds-on-t he-bot tom

medic al-fa cil ity-status-fa cil ity-id (FK) obje ct-i tem-status-in dex (FK ) medic al-fa cil ity-status-in te rval-ca sual ty -typ e-inde x medic al-fa cil ity-status-in te rval-ca sual ty -typ e-code medic al-fa cil ity-status-in te rval-ca sual ty -typ e-arri val -count medic al-fa cil ity-status-in te rval-ca sual ty -typ e-admitted-c ount

VE RTI CAL-DIS TANCE vertical -distan ce-id

poi nt-category-co de

ORBI T-ARE A orbi t-area -i d (FK)

is-first-poin t -f or / is-def ined-using

orbi t-area -a lig nment-cod e orbi t-area -w idth-di mensi on orbi t-area -first-poi nt-id (FK ) orbi t-area -s econd -point-i d (FK)

is-second-point-f or / is-def in ed-using

vertical -distan ce-referen ce-code vertical -distan ce-dime nsio n vertical -distan ce-preci sion -c ode vertical -distan ce-datum-text

F AN-AREA fan-area -id (FK )

RELATI VE-POINT re lative-poin t-i d (FK)

ABS OLUTE-POINT ab solu te -p oint-id (FK) ab solu te -p oint-cate gory-code ab solu te -p oint-ve rti cal-di stance -i d (FK)

re lative-poin t-x-c oordin ate-dimen sion re lative-poin t-y-c oordin ate-dimen sion re lative-poin t-z-c oordin ate-dimen sion re lative-poin t-x-p re cisi on-cod e re lative-poin t-y-p re cisi on-cod e re lative-poin t-z-p re cisi on-cod e re lative-coordi nate-sys te m-i d (FK)

is-the-vertex-f or / is-def ined-usin g

fan-area -minim um-ra nge-di mensi on fan-area -maximu m-ran ge-dime nsio n fan-area -orientati on-angl e fan-area -sector-siz e-angl e fan-area -vertex-poi nt-id (FK ) TRACK-AREA trac k-area-id (FK)

is-begin ning-point -for /

MEDICAL-FACILIT Y-STATUS-PE NDING-S URGERY me dica l-fac ili ty-status-fac ili ty-id (FK ) o bjec t-i te m-s tatus-ind ex (FK) me dica l-fac ili ty-status-pend ing-su rg ery-inde x me dica l-fac ili ty-status-pend ing-su rg ery-tri age-co de me dica l-fac ili ty-status-pend ing-su rg ery-coun t

s urface -c ategory-co de

constit ut es-the-set -of -waypoints-f or / is-def ined-using is-used-to-def ine / has-as-its-bearing-orig in

sph ere-vol ume-id (FK) sph ere-vol ume-radiu s-dimen sion sph ere-vol ume-centre-po int-id (FK)

has

medi cal-facil ity-status-ca sual ty -b ed-occu pancy -g roup-cod e medi cal-facil ity-status-ca sual ty -b ed-occu pancy -c ount

poin t-c ategory-cod e

is-t he-centre-f or / has-as-its-centre

SPHERE-VOLUME

UX O-ST ATUS uxo -status-id (FK) obj ect-item-status -i ndex (FK)

ME DI CAL-FACILI TY-STAT US-I NT ERV AL-CASUALTY-TY PE

has

M EDI CA L-FA CI LI TY-STA TUS -CAS UALTY -B ED-OCCUPANCY medi cal-facil ity-status-facil ity-id (FK) obj ect-item-status-i ndex (FK) medi cal-facil ity-status-ca sual ty -b ed-occu pancy -i ndex

makes-ref erence-to is-part -of -the-boundary-f or

CONE -V OLUME cone -volume -id (FK )

is-specif ied-f or has

MI NEF IELD-MA RI TIME mi nefi eld -ma ri time-id (FK)

minefiel d-land -d epth-pl acemen t-co de minefiel d-land -functi on-code minefiel d-land -p attern-code minefiel d-land -p ersiste nce-cod e minefiel d-land -s toppin g-power-cod e

min efi eld-mari ti me-id (FK) min efi eld-mari ti me-casu alty-esti mate-ind ex min efi eld-mari ti me-casu alty-esti mate-averag e-coun t min efi eld-mari ti me-casu alty-esti mate-given-transit-co unt

su rface-c ategory-cod e

lin e-poin t-se quenc e-ordina l lin e-poin t-po int-id (FK) is-used-as /

poin t-i d (FK)

has-as-its-vertex

inclu des-report -of / report-is-part-of

ai rfiel d-status-id (FK) obj ect-item-status -i ndex (FK) ai rfiel d-status-day -o peration s-code ai rfiel d-status-fl igh t-su pport-category -c ode ai rfiel d-status-eva luati on-ind icator-co de ai rfiel d-status-maxi mum-nbac -th ro ughpu t-co unt ai rfiel d-status-maxi mum-nbac -park-coun t ai rfiel d-status-maxi mum-wbac -throu ghput-co unt ai rfiel d-status-maxi mum-wbac -p ark-count

SURF ACE su rface-i d (FK)

is-def ined-using / is-used-in-the-def inition-of P

LI NE-POINT lin e-id (FK) lin e-poin t-i ndex

P OI NT

geometri c-volu me-category -c ode

materiel-statu s-category-code

med ical -faci lity-status -interval -evac uation -d estina ti on-cod e med ical -faci lity-status -interval -evac uation -c ount

AIRFIE LD-STAT US

mi nefield -c ategory-co de

MI NE FIELD-LA ND minefiel d-land -i d (FK)

MINEFI ELD-MARIT IME-CASUALTY-EST IMATE

is-endpoint-of-x-vector-f or / is-def in ed-using is-endpoint-of -y-vect or-f or / is-def ined-using

ge ometric-vo lume-ca te gory-cod e ge ometric-vo lume-l ower-vertica l-dis ta nce-id (FK) ge ometric-vo lume-up per-vertica l-dis ta nce-id (FK)

ma teriel-s ta tu s-category-co de ma teriel-s ta tu s-body-co lour-cod e ma teriel-s ta tu s-marking -c ode ma teriel-s ta tu s-marking -c olou r-co de ma teriel-s ta tu s-demol ition -s ta tu s-code ma teriel-s ta tu s-imo-comp lia nt-i ndi cator-code ma teriel-s ta tu s-operatio nal-status -code ma teriel-s ta tu s-operatio nal-status -qual ifi er-c ode ma teriel-s ta tu s-operatio nal-status -mode-cod e ma teriel-s ta tu s-re serve-i ndic ator-c ode ma teriel-s ta tu s-safe ty -s ta tu s-code ma teriel-s ta tu s-usage -s ta tu s-code

MEDICAL-FACILITY-S TATUS-INTERVAL-EVACUATI ON med ical -faci lity-status -faci lity-i d (FK) obj ect-item-status -i ndex (FK) med ical -faci lity-status -interval -evac uation -i ndex

includes-report -of / report -is -part -of

med ical -faci lity-status -surgery-bac klog -d uration

mi litary-ob stacle -c ategory-co de

mi nefi eld -c ategory-co de mi nefi eld -i denti fic ation-text mi nefi eld -mi ne-spa cing -d imens ion

LINE line -id (FK )

is-origin-for / is-def ined-using

o bjec t-reference-ob ject-ite m-i d (FK) o bjec t-reference-l ocatio n-id (FK) o bjec t-reference-ob ject-ite m-l ocati on-ind ex (FK)

used-f or-expression-of /

facility-sta tus-category-code

MEDICAL-FACILITY -S TATUS med ical -faci lity-status -faci lity-i d (FK) obj ect-item-status -i ndex (FK)

mili tary-obstacl e-catego ry -c ode

MINEF IELD mi nefi eld -i d (FK)

loca tion-ca te gory-code

poin t-reference-ori gin-po int-id (FK) poin t-reference-x-vector-poin t-i d (FK) poin t-reference-y-vector-poin t-i d (FK)

expressed-w ith-ref erence-t o

organi sation -s ta tu s-id (FK) obje ct-i tem-status-in dex (FK )

network-freq uency -b and-co de network-freq uency -c hanne l-numb er-tex t network-freq uency -d iscrete -frequen cy-quan ti ty network-freq uency -b and-lo wer-freque ncy-qua ntity network-freq uency -b and-up per-freque ncy-qua ntity network-freq uency -e ffe ctive -s ta rt-dateti me network-freq uency -e ffe ctive -e nd-datetime network-freq uency -m odula tion-co de network-freq uency -p urpose -tex t

provid es-geometric-def inition-f or

l ocatio n-catego ry -c ode

POI NT-REFERENCE re lative-coordi nate-sys te m-i d (FK)

MAT ERIEL-STATUS ma teriel-s ta tu s-id (FK ) o bjec t-i te m-status-ind ex (FK)

organi sation -s ta tu s-operati onal -s ta tu s-code organi sation -s ta tu s-operati onal -s ta tu s-qual ifi er-code organi sation -s ta tu s-avai lab ili ty -code organi sation -s ta tu s-comman d-and-con trol -role-co de organi sation -s ta tu s-commi tme nt-s ta tus-code organi sation -s ta tu s-fire-mo de-code organi sation -s ta tu s-cbrn-dress -s ta te -code organi sation -s ta tu s-radia ti on-dos e-quanti ty organi sation -s ta tu s-readi ness-co de organi sation -s ta tu s-readi ness-du ra ti on organi sation -s ta tu s-reinforcemen t-co de organi sation -s ta tu s-reserve-i ndic ator-code organi sation -s ta tu s-tra ini ng-code organi sation -s ta tu s-usag e-status-code

FACILI TY-STAT US facil ity-status -i d (FK) o bjec t-i te m-s ta tu s-inde x (FK)

NETWORK-FREQUENCY network-id (FK) network-freq uency -i ndex

MI LI TARY-OBSTACLE mili tary-obstacl e-id (FK)

berth-dea dwei ght-to nnage -q uantity berth-dep th -dimen sion berth-le ngth-dime nsio n berth-lo cation -tex t berth-maj or-vesse l-cla ss-code berth-maxi mum-bea m-d imens ion berth-maxi mum-cap acity-qu antity berth-maxi mum-ves sel-co unt berth-day -l imi t-ne t-e xplo sive -q uantity berth-ni ght-limi t-n et-expl osive-quanti ty berth-rail -avai labi li ty -i ndi cator-code berth-roll -on-roll -o ff-i ndic ator-c ode berth-turnarou nd-time-durati on

dry-do ck-boa t-l ift-cap acity-qu antity dry-do ck-dep th -d imens ion dry-do ck-len gth-dime nsio n dry-do ck-loc ation-tex t dry-do ck-marin e-ra ilwa y-size -c ode dry-do ck-wid th -d imens ion dry-do ck-worksh op-code

LIQUID-S URFACE-STA TUS l iqu id-surface-status-i d (FK) o bjec t-i te m-s tatus-ind ex (FK)

ORGA NI SATI ON-STATUS

NETWORK -CAP ACI TY ne twork-id (FK) ne twork-capac ity-ind ex

ancho ra ge-bottom-type-co de ancho ra ge-day-l imit-net-exp losi ve-qu antity ancho ra ge-draugh t-hi gh-tide -dimen sion ancho ra ge-draugh t-l ow-tide-di mensi on ancho ra ge-len gth-dimen sion ancho ra ge-moorin gs-type-co de ancho ra ge-nig ht-l imi t-ne t-ex plos ive -q uantity ancho ra ge-preva ili ng-win d-directi on-code ancho ra ge-vess el-tonn age-qua ntity ancho ra ge-width -d imens ion

LOCATI ON l ocatio n-id

relative-coordinate-syste m-reference-category-code

GEOM ETRIC-V OLUME ge ometric-vo lume-i d (FK)

uses / is-specified-for has / is-specified-f or

ANCHORAGE ancho ra ge-id (FK)

BERTH berth-id (FK)

DRY-DOCK dry-do ck-id (FK)

provides-geometric-def init ion-f or

rela tive-co ordina te -s ystem-id rela tive-co ordina te -s ystem-refe re nce-categ ory-code

provides-coordin ate-f rame-ref erence-f or

S OLID-SURF ACE -S TATUS soli d-surfa ce-status-i d (FK) obje ct-item-status-in dex (FK) soli d-surfa ce-status-co de soli d-surfa ce-status-de moli ti on-status-co de soli d-surfa ce-status-su rface-co nditi on-code soli d-surfa ce-status-su rface-firmness -c ode soli d-surfa ce-status-ve getatio n-code

person-s ta tu s-duty-status-co de person-s ta tu s-physi cal -s ta tu s-code person-s ta tu s-physi cal -s ta tu s-qual ifi er-code person-s ta tu s-ra diati on-dose -q uantity person-s ta tu s-re serve-i ndic ator-c ode

network-servi ce-status -i ndic ator-code re porting-da ta -i d (FK)

ne twork-capac ity-ban dwidth-co de ne twork-capac ity-protoco l-code

bas in-dea dweig ht-to nnage -q uantity bas in-dep th -d imens ion bas in-le ngth-dime nsio n bas in-lo cation -tex t JE TTY j etty-id (FK )

s lip way-gradi ent-angl e s lip way-len gth-dime nsion s lip way-loc ation-tex t s lip way-wid th -d imens ion

has /

ne two rk-servic e-catego ry -c ode ne two rk-servic e-subca tegory-cod e

referen ce-ass ociati on-categ ory-code

RE LA TIVE -COORDINATE-SY STEM

provides / is-provid ed-by

BASI N bas in-id (FK)

SLIP WAY s lip way-id (FK)

P ERS ON-STAT US person-s ta tu s-id (FK ) obje ct-i tem-status-in dex (FK)

can-be-accessed-via /

NETWORK -S ERV ICE ne two rk-id (FK ) ne two rk-servic e-inde x

geographic-feature-status-cate gory-code

con trol -feature -s ta tu s-inve stigati on-status-co de con trol -feature -s ta tu s-cbrn-threat-level-cod e con trol -feature -s ta tu s-securi ty -s tatus-code con trol -feature -s ta tu s-usage -s ta tus-code

provides-access-t o

netwo rk -c ategory-cod e netwo rk -s ubcateg ory-code netwo rk -a rc hitecture-co de netwo rk -c hanne l-coun t netwo rk -ma ximum-ca paci ty -q uantity netwo rk -mi nimu m-c apaci ty-quanti ty netwo rk -me ans-cod e netwo rk -c ry ptographi c-ind icator-cod e netwo rk -c ry ptographi c-pla n-short-title-text netwo rk -c ry ptographi c-code -s hort-ti tle-text netwo rk -s ecurity-cl assi fi cation -c ode netwo rk -s ecurity-cl assi fi cation -c aveat-text netwo rk -s ecurity-po lic y-code netwo rk -s et-n umber-cou nt

HARB OUR ha rbour-id (FK)

CONTROL-FEAT URE-STA TUS con trol -feature -s ta tu s-id (FK) obj ect-item-status -i ndex (FK)

physi cal -a ddress-ca te gory-cod e physi cal -a ddress-resi denc e-te xt physi cal -a ddress-street-text physi cal -a ddress-street-ad ditio nal-text physi cal -a ddress-po stal-box -te xt physi cal -a ddress-po stbox-id entifier-text physi cal -a ddress-ci ty-te xt physi cal -a ddress-ge ographi c-text physi cal -a ddress-po stal-cod e-text

elec tron ic-add ress-name -tex t network-id (FK) network-service-i ndex (FK)

NE TWORK netwo rk -i d (FK)

materie l-seria l-numbe r-i dentifica ti on-text materie l-lot-id entificati on-text materie l-hul l-numbe r-text materie l-mine -req uisi tion-ca se-numbe r-tex t

REF ERE NCE-ASS OCIAT ION referen ce-ass ociati on-sub ject-refe re nce-id (FK) referen ce-ass ociati on-obj ect-referen ce-id (FK) referen ce-ass ociati on-ind ex

obj ect-item-loc ation-verti cal -a ccuracy -d imens ion obj ect-item-loc ation-ho ri zontal -accura cy-dime nsio n obj ect-item-loc ation-be aring-an gle obj ect-item-loc ation-be aring-ac curacy -a ngle obj ect-item-loc ation-be aring-pre cisi on-code obj ect-item-loc ation-i ncli natio n-angl e obj ect-item-loc ation-i ncli natio n-accurac y-angl e obj ect-item-loc ation-i ncli natio n-precis ion-co de obj ect-item-loc ation-sp eed-rate obj ect-item-loc ation-sp eed-acc uracy-rate obj ect-item-loc ation-sp eed-prec isio n-code obj ect-item-loc ation-mea ning -c ode reporting -d ata-id (FK)

ge ographi c-fea tu re -status-catego ry -c ode ge ographi c-fea tu re -status-mine -p re sence -c ode ge ographi c-fea tu re -status-surfa ce-recircu latio n-indi cator-code

P HYS ICAL-A DDRESS address -i d (FK)

E LE CTRONI C-ADDRE SS address -id (FK )

OBJECT -I TEM-LOCAT ION obj ect-item-id (FK) loc ation-i d (FK) obj ect-item-loc ation-i ndex

GEOGRAPHIC-FEAT URE-STAT US ge ographi c-fea tu re -status-id (FK) ob ject-item-s ta tu s-inde x (FK)

object-item-st at us-category-code

address-category-code

bridge -l onge st-s pan-le ngth-dime nsio n bridge -s pan-cou nt bridge -u sage-co de

materie l-id (FK)

pe rs on-birth-da te ti me pe rs on-blo od-type-co de pe rs on-gend er-code pe rs on-profe ssin g-indi cator-cod e

GEOGRAPHIC-FEAT URE ge ograph ic-fea ture-id (FK )

A FFILIA TION-GEOPOLI TICAL affili ation-i d (FK)

SURFACE-VESS EL-T YPE

MI LITARY-ORGANISA TION-T YPE mili tary-organi sation -ty pe-id (FK)

ad dress-categ ory-code ad dress-pl ace-name -te xt

a irfi eld-ai r-traffic -c ontrol-prese nce-in dica to r-c ode a irfi eld-ha ngar-area-qua ntity a irfi eld-i nstrument-lan ding -s ystem-prese nce-in dica to r-co de a irfi eld-i nternation al-ci vil -a viati on-organ isatio n-code a irfi eld-vi sual -navi gation al-ai d-indi cator-code BRIDGE bridge -i d (FK)

is-administered-by

organi sation -reference -a ssoci ation -c ategory-co de

provides-applicable-inf ormat ion-f or / is-ref erenced-to

o bjec t-i te m-s ta tu s-catego ry -c ode o bjec t-i te m-s ta tu s-hosti lity-co de o bjec t-i te m-s ta tu s-boob y-trap -p re sence -c ode o bjec t-i te m-s ta tu s-emis sion-c ontrol-cod e rep orti ng-data-i d (FK)

is-ref erence-for

ADDRESS ad dress-id

AI RF IELD a irfi eld-i d (FK)

is-ref erenced-in

feature-ca te gory-code

applies-to

ORGANIS ATION-REF ERE NCE-ASS OCIAT ION organi sation -i d (FK) re ferenc e-id (FK ) organi sation -reference -a ssoci ation -i ndex

OBJECT-IT EM-STAT US o bjec t-i te m-i d (FK) o bjec t-i te m-s ta tu s-inde x

is-assigned-through

obj ect-item-add re ss-cal l-sig n-te xt obj ect-item-add re ss-primac y-code obj ect-item-add re ss-authori sation -i ndi cator-code obj ect-item-add re ss-tra nsmit-rece ive-co de network-i d (FK) network-fre quenc y-inde x (FK) reportin g-data-id (FK)

fac ili ty-category -c ode

MATERIE L

PERSON pe rs on-id (FK)

featu re -c ategory-cod e

affili ation-eth nic-grou p-code

group-organ isati on-type-cate gory-code

P

o bjec t-type -reference -a ssoci ation -c ategory-co de provides-applicable-inf ormation-f or / is-ref erenced-t o

OBJECT-ITEM-ADDRE SS obj ect-item-id (FK) addres s-id (FK) obj ect-item-add re ss-ind ex

fac ili ty-category-co de fac ili ty-primary-con struction -ma te ri al-co de fac ili ty-base-i dentifica ti on-cod e-te xt fac ili ty-heig ht-d imens ion fac ili ty-leng th -d imens ion fac ili ty-width-di mensi on fac ili ty-major-bui ldi ng-type-i d (FK)

OBJECT -I TEM-AF FILIAT ION obje ct-i tem-id (FK) affili ation -i d (FK) obje ct-i tem-affili ation -i ndex

is-assigned-through

F EATURE featu re -i d (FK)

AF FILIA TION-ET HNIC-GROUP affili ation-i d (FK)

GROUP-ORGANISAT ION-TY PE

is-established-by

is-est ablished-by

OBJECT-TY PE-RE FERENCE-AS SOCIA TION o bjec t-type -i d (FK) reference -i d (FK) has / is-ascrib ed-to

has-for-address /

a ffi lia ti on-id (FK)

s ubsurface-ves sel-type -category-co de s ubsurface-ves sel-type -dive d-disp lace ment-quanti ty s ubsurface-ves sel-type -speed -c avitati on-quan ti ty s ubsurface-ves sel-type -to rp edo-lo adin g-gear-ind icator-cod e

is-ascribed-to

establishes /

is-the-address-f or

FACILITY fac ili ty-id (FK )

affiliation-category-code

wea pon-type-i d (FK)

is-the-subject -of

est ablishes /

affili ation -c ategory-cod e

WEAP ON-TYPE

is-established-by

has /

provides-applicable-in f ormation-for / is-ref erenced-to

P

UNI T u nit-id (FK)

con voy-day -s peed-rate con voy-day -vehi cle-ga p-dimen sion con voy-hal t-d uration con voy-ni ght-speed -ra te con voy-ni ght-vehi cle-g ap-dime nsio n con voy-pac ket-gap-di mensi on con voy-pac ket-size -c ount

is-specified-through / is-a-component -of

ob ject-type -e stabli shmen t-effec ti ve-date ti me ob ject-type -e stabli shmen t-ca te gory-cod e ob ject-type -e stabli shmen t-en viron ment-condi tion-co de ob ject-type -e stabli shmen t-na me-text ob ject-type -e stabli shmen t-op erationa l-mode-c ode

a ffi lia ti on-fu nction al-group -code a ffi lia ti on-fu nction al-group -name-text

gove rn ment-organi satio n-ty pe-catego ry-code gove rn ment-organi satio n-ty pe-main -a ctivi ty-code

has /

is-t he-obje ct-of

OBJECT-TYP E-ESTAB LI SHMENT es tabli shed-ob ject-type -i d (FK) ob ject-type -e stabli shmen t-i ndex

AFF ILIAT ION-FUNCTI ONAL-GROUP

GOVERNM ENT -ORGA NI SATI ON-TYPE gove rn ment-organi satio n-ty pe-id (FK)

P

c ontext-asse ssment-text c ontext-asse ssment-effecti ve-dateti me c ontext-asse ssin g-organi sation -i d (FK)

provides-applicable-inf ormation-f or / is-ref erenced-to

org anisa tion-ca te gory-code

CONVOY con voy-id (FK)

is-made-up-t hrough / specif ies-the-composition-of

A FFILI ATION affili ation -i d

vessel-type-category-code

is-cit ed-by

CONTEX T-ASSES SMENT c ontext-id (FK) c ontext-asse ssment-in dex

provides

provides-applicable-inf ormation-for / is-ref erenced-to is-geometrically-def ined-through

has-relevant-informat ion-in

is-specified-as-part -of / ref erences

VESSE L-TY PE ves sel-type -id (FK )

SUBSURFACE-VESS EL-T YPE s ubsurface-ves sel-type -id (FK )

identif ies-the-data-f or

reportin g-data-id (FK)

organ isati on-catego ry -c ode

obj ect-item-obj ect-type-es ta bli shment-effecti ve-datetim e

surfac e-vess el-type-ca te gory-code surfac e-vess el-type-di spl acemen t-qu antity surfac e-vess el-type-max imum-dec k-load -q uantity

has-as-constit uent-part / is-a-part-of

CONTEXT-ELEME NT contex t-i d (FK) contex t-e lemen t-i ndex

o has-a-role-w ith-respect-tis-ascribed-t o

grou p-characteri stic-ag e-group-cod e grou p-characteri stic-mal ady-co de grou p-characteri stic-mal ady-transmi ssi bil ity-ind icator-cod e grou p-characteri stic-ge nder-code grou p-characteri stic-la nguag e-code grou p-characteri stic-triag e-code

o bjec t-type -e stabli shmen t-ob ject-type -d etail -ma jor-part-indi cator-cod e o bjec t-type -e stabli shmen t-ob ject-type -d etail -c ount o bjec t-type -e stabli shmen t-ob ject-type -d etail -o bjec t-type -i d (FK) o bjec t-type -e stabli shmen t-de tail-ob ject-type -e stabli shmen t-i ndex (FK)

id entif ies-establishment-f or-detail-object -type-in / ref erences

ra ilc ar-typ e-id (FK)

reporting -d ata-abso lute-timi ng-effective-start-d atetime reporting -d ata-abso lute-timi ng-effective-end-dateti me

is-the-report ing-agent-f or /

has

OBJECT-TY PE-ESTA BLI SHMENT-OB JECT-TYPE -DETA IL e stabli shed -o bjec t-type -i d (FK) o bjec t-type -e stabli shmen t-i ndex (FK) o bjec t-type -e stabli shmen t-ob ject-type -d etail -i ndex

OBJECT-TY PE-AFFI LI ATI ON o bjec t-type -i d (FK) a ffi lia ti on-id (FK)

is-ascribed-to

ra ilc ar-typ e-category-c ode ra ilc ar-typ e-subca te gory-cod e ra ilc ar-typ e-gauge -d imens ion

REP ORTING-DAT A-ABSOLUTE -TIMI NG reporting -d ata-abso lute-timi ng-reporting -d ata-id (FK)

provi des-ap pli cable -info rm ation-for / is-referenced -to

has-a-role-wit h-respect-to

biol ogi cal-materi el-type-ca te gory-cod e biol ogi cal-materi el-type-su bcatego ry -code biol ogi cal-materi el-type-pe rs istenc y-code

chemi cal-materi el-type-ca te gory-cod e chemi cal-materi el-type-su bcatego ry-code chemi cal-materi el-type-pe rs istenc y-code

radi oactive-materiel -ty pe-catego ry-code radi oactive-materiel -ty pe-primary -rad iatio n-code

ma ritime-eq uipme nt-typ e-category -c ode ma ritime-eq uipme nt-typ e-subca te gory-cod e

RAILCAR-TYPE

P

reportin g-data-relati ve-timi ng-offset-duratio n reportin g-data-relati ve-timi ng-referen ce-actio n-task-id (FK)

is-reported-by

CHEMICAL-MATERIE L-TY PE chemi cal-materi el-type-i d (FK)

RA DI OA CTI VE-MATE RI EL-T YPE radi oactive-materiel -ty pe-id (FK)

ENGI NE ERI NG-EQUI PMENT-TYP E

MARIT IME-EQUIPME NT-T YPE ma ritime-eq uipme nt-typ e-id (FK)

misce lla neous -e quip ment-type-categ ory-code misce lla neous -e quip ment-type-sub category-co de

ves sel-type -category-co de ves sel-type -magneti c-degau ssin g-code-nu mber-quanti ty ves sel-type -prismati c-coeffici ent-ratio ves sel-type -dead-wei ght-quan tity ves sel-type -draught-di mensi on ves sel-type -gross-regi stered-tonnag e-quan ti ty ves sel-type -heigh t-a bove-the-wa te rl ine -d imens ion ves sel-type -propel ler-coun t ves sel-type -propul sion-typ e-code ves sel-type -operatio nal-di spla cemen t-qu antity

RE PORTI NG-DA TA-RE LA TIVE -T IMING reportin g-data-relati ve-timi ng-reporting -d ata-id (FK)

is-conf g i ured-as-specif ied-in /

GROUP-CHARACTERISTI C grou p-characteri stic-id provides-categorisat ion-f or / is-classif ied-according-t o

re ferenc e-approval-dateti me re ferenc e-content-cate gory-code re ferenc e-creation -d atetime re ferenc e-descri ption-text re ferenc e-elec tron ic-sou rc e-text re ferenc e-fil e-siz e-quanti ty re ferenc e-format-text re ferenc e-lang uage-co de re ferenc e-lifecyc le-cod e re ferenc e-mediu m-typ e-code re ferenc e-origi nator-te xt re ferenc e-physi cal -s ize-text re ferenc e-primary-lo cation -te xt re ferenc e-publ icati on-datetime re ferenc e-re leas abil ity-text re ferenc e-securi ty -c lass ifi catio n-code re ferenc e-short-title-text re ferenc e-ti tle-text re ferenc e-tran smittal-typ e-code re ferenc e-vali dity-pe ri od-beg in-date ti me re ferenc e-vali dity-pe ri od-end -datetime re ferenc e-verificati on-code re ferenc e-versio n-text

reporting-data-timing-category-code

obj ect-item-ass ocia ti on-sub ject-obj ect-item-i d (FK) obj ect-item-ass ocia ti on-obj ect-obj ect-item-id (FK) obj ect-item-ass ocia ti on-in dex (FK) obj ect-item-ass ocia ti on-status -i ndex obj ect-item-ass ocia ti on-status -c ategory-cod e reportin g-data-id (FK)

specif ies-the-conf iguration-of

is-enumerat ed-in /

context-category-code

is-t he-object-of

provides-applicable-inf ormat ion-f or / is-ref erenced-to

OB JECT-ITEM -A SSOCI ATION-STATUS

is-cited-in / is-referenced-to

REFERENCE re ferenc e-id

provides-inf ormation-related-to / is-amplif ied-by

re porting-da ta -i d (FK)

has / is-ascribed-t o

is-part-of

cbrn-eq uipme nt-ty pe-catego ry -c ode

ele ctronic -e quip ment-ty pe-catego ry-code ele ctronic -e quip ment-ty pe-subc ategory-co de

includes / is-an-element-of P

obj ect-item-ass ocia ti on-sub ject-obj ect-item-id (FK) obj ect-item-ass ocia ti on-obj ect-obj ect-item-id (FK) obj ect-item-ass ocia ti on-in dex (FK )

is-referenced-in / ref ers-t o

obje ct-i tem-assoc iatio n-category-c ode obje ct-i tem-assoc iatio n-subca te gory-cod e action -tas k-id (FK)

ORGANI SATI ON organ isati on-id (FK)

BI OLOGICAL-MA TERIEL-TYPE biol ogi cal-materi el-type-i d (FK)

a ircraft-type-i d (FK) a ircraft-type-c ategory-cod e a ircraft-type-s ubcateg ory-code a ircraft-type-mo del-co de a ircraft-type-l oad-ca te gory-code a ircraft-type-tak eoff-and-la nding -code a ircraft-type-wi ng-spa n-dimen sion CB RN-EQUI PMENT-TYPE cbrn-eq uipme nt-ty pe-id (FK)

ELECT RONIC-E QUIP MENT-TYPE ele ctronic -e quip ment-ty pe-id (FK)

provides-applicable-informat ion-f or / is-ref erenced-to

ORGANIS ATION-STRUCTURE

ORGANI SATI ON-STRUCTURE-DE TAIL organi satio n-structure-root-organi satio n-id (FK ) organi satio n-structure-ind ex (FK) organi satio n-structure-detai l-ind ex

OBJE CT-I TEM-ASS OCIAT ION obje ct-i tem-assoc iatio n-subj ect-obje ct-i tem-id (FK) obje ct-i tem-assoc iatio n-obje ct-o bjec t-i te m-id (FK ) obje ct-i tem-assoc iatio n-inde x

ob ject-ite m-g ro up-acco unt-name-text ac tion-id (FK) rep orti ng-data-i d (FK)

obj ect-item-group -accou nt-d etail -c ount obj ect-item-group -accou nt-d etail -q uali fie r-c ode group -c haracteris tic-id (FK) perso n-ty pe-id (FK)

reportin g-data-id reportin g-data-accu ra cy-cod e reportin g-data-catego ry-code reportin g-data-coun ti ng-in dica to r-c ode reportin g-data-credi bil ity-code reportin g-data-reli abil ity-cod e reportin g-data-reportin g-datetime reportin g-data-source -ty pe-code reportin g-data-timin g-catego ry -c ode reportin g-data-real-da ta-exerci se-use-on ly-cod e refe re nce-id (FK) reportin g-data-reportin g-organi sation -i d (FK)

provides-applic able-inf ormation-f or /

is-specif ied-f or / requires-the-use-of

o bjec t-i te m-a lia s-category -c ode o bjec t-i te m-a lia s-name-text

has-an-associat ed / is-associat ed-w ti h

assigns-report ing-code-in

a mmuniti on-type-ca te gory-code a mmuniti on-type-ca libre-tex t a mmuniti on-type-mi ne-maritime -firin g-code

eng inee ri ng-equ ipmen t-typ e-id (FK )

applies-to

RE PORTI NG-DA TA

provides-applicable-in f ormation-for / is-ref erenced-to

h oldi ng-ope ra ti onal -count h oldi ng-total-co unt rep orti ng-data -i d (FK)

obj ect-item-id (FK) obj ect-type-id (FK) obj ect-item-type-i ndex reportin g-data-id (FK)

is-t he-object-of is-the-ow ner-of

ident fi ies-the-major-building-t ypes-in-a

ob ject-ite m-i d (FK) ob ject-ite m-g ro up-acco unt-inde x

has-relevant-inf ormation-in is-t he-object-of

rule-of-engag ement-id rule-of-engag ement-name -tex t rule-of-engag ement-desc ription -te xt owni ng-organ isatio n-id (FK)

OBJECT-IT EM-GROUP -A CCOUNT OB JECT-ITEM -GROUP-ACCOUNT-DET AIL obj ect-item-id (FK) obj ect-item-group -accou nt-i ndex (FK) obj ect-item-group -accou nt-d etail -i ndex

AMM UNITI ON-TYP E a mmuniti on-type-id (FK)

eng inee ri ng-equ ipmen t-typ e-category-co de

c ontext-reporting -data-asso ciati on-catego ry -c ode est ablishes / is-established-by

o bjec t-i te m-i d (FK) o bjec t-type -i d (FK) h oldi ng-in dex

OB JECT-ITEM -T YPE

RULE-OF-ENGAGEMENT

specif ies

cons umabl e-materiel -typ e-category -c ode cons umabl e-materiel -typ e-subca te gory-cod e cons umabl e-materiel -typ e-hazard-c ode cons umabl e-materiel -typ e-issu ing-el ement-cod e cons umabl e-materiel -typ e-issu ing-co unt cons umabl e-materiel -typ e-issu ing-un it-of-meas ure-code cons umabl e-materiel -typ e-issu ing-we ight-qua ntity cons umabl e-materiel -typ e-perish abil ity-in dica to r-co de cons umabl e-materiel -typ e-united -n ations -number-cod e

MI SCELLA NEOUS-EQUI PMENT-TYPE misce lla neous -e quip ment-type-id (FK)

CONTEX T-RE PORTI NG-DA TA-ASSOCIAT ION c ontext-id (FK) rep orti ng-data-i d (FK) c ontext-reporting -data-asso ciati on-ind ex

o bjec t-i te m-reference -a ssoci ation -c ategory-co de o bjec t-i te m-reference -a ssoci ation -s peci fic -p art-tex t

HOLDING

has / belongs-to si -classif ied-as

has

CONS UMA BLE-MATERIE L-TYP E cons umabl e-materiel -typ e-id (FK)

equip ment-type-category-code

has /

is-the-subject -of

OBJECT-IT EM-RE FERENCE-AS SOCI ATION o bjec t-i te m-i d (FK) reference -i d (FK) o bjec t-i te m-reference -a ssoci ation -i ndex

is-part-of

uses-as-timing-ref erence

obje ct-i tem-category-c ode obje ct-i tem-name-text

is-a-const raint-on

P

rou te -typ e-catego ry -c ode

c

si -the-object-of

is-ascribed-to P

REQUEST -A NS WER-E LEM ENT requ est-id (FK ) requ est-answer-i ndex (FK) repo rti ng-data-id (FK)

is-comprised-of

reques t-a nswer-categ ory-code reportin g-data-id (FK)

serves-as-t iming-ref erence-f or /

a ction-task -i d (FK) rul e-of-en gageme nt-i d (FK)

organ isati on-actio n-task-rule -o f-enga gement-status -c ategory-cod e organ isati on-actio n-task-rule -o f-enga gement-status -e ffec tive-start-dateti me organ isati on-actio n-task-rule -o f-enga gement-status -e ffec tive-en d-datetime o bjec t-i te m-c ategory-co de

ROUTE-TY PE rou te -typ e-id (FK)

REQUEST-ANSWE R reques t-i d (FK) reques t-a nswer-ind ex

results-in / is-a-response-to

OBJE CT-I TEM obje ct-i tem-id

ACTION-TASK-RULE-OF-ENGAGE MENT

has

ORGANISAT ION-ACTION-TASK-RULE-OF-ENGAGE MENT-STATUS acti on-task-id (FK) rule -o f-enga gement-i d (FK) organ isati on-actio n-task-rule -o f-enga gement-status -o rg anis ation-i d (FK) organ isati on-actio n-task-rule -o f-enga gement-status -i ndex

ORGANISA TION-MA TERIEL-TYPE -A SSOCI ATION org anisa tion-id (FK) ma te ri el-type -i d (FK) org anisa tion-materi el-type-as soci ation-repo rta ble-type -c ode org anisa tion-materi el-type-as soci ation-repo rta ble-type -tex t org anisa tion-materi el-type-as soci ation-repo rta ble-type -d atetime

control-feature-type-category-code

CONTEXT-AS SOCI ATION is-the-subje ct-of

c ontext-catego ry -code c ontext-name-tex t c ontext-secu ri ty-clas sificati on-code

is-the-subject-of

RE QUEST

provides-applicable-informat ion-f or / is-ref erenced-t o

is-ascribed-t o

CONTEX T c ontext-id

co ntext-obje ct-item-asso ciati on-catego ry -c ode

is-used-as-a-classif icat o i n-f or is-aut hority-f or-t he-use-of / is-used-as-specif ied-by

person -typ e-category-c ode person -typ e-subca te gory-cod e person -typ e-ra nk-code

materiel -ty pe-catego ry -c ode

con trol -feature-type -c ategory-co de

is-const ituted-t o-support

acti on-loc ation-ac curacy-di mensi on acti on-loc ation-be aring-an gle reportin g-data-id (FK)

con text-obje ct-i tem-assoc iatio n-status-categ ory-code con text-obje ct-i tem-assoc iatio n-status-effective-datetime con text-obje ct-i tem-assoc iatio n-status-estab lis hing-o rg anis ation-i d (FK)

has /

CONTEX T-OBJECT-ITEM-A SSOCI ATION co ntext-id (FK) ob ject-item-i d (FK)

is-subject -of / ref erences /

P ERSON-TYPE person -typ e-id (FK)

is-assigned-report ing-code-in

fea tu re -typ e-catego ry -c ode

feature-typ e-category-co de

CONTROL-FEAT URE-TYPE con trol -feature-type -i d (FK)

task-fo rma ti on-type -c ategory-cod e

ACTION-LOCA TION acti on-id (FK) lo cation -i d (FK) acti on-loc ation-i ndex

CONTEXT -OBJECT -I TEM-AS SOCIA TION-S TATUS con text-id (FK ) obj ect-item-i d (FK) con text-obje ct-i tem-assoc iatio n-status-in dex

establishes / si -established-by

obje ct-i tem-id (FK)

is-constrained-by

materi el-type-ca tegory-cod e materi el-type-rep orta ble-i te m-tex t materi el-type-sto ck-numbe r-text materi el-type-su pply -c lass -c ode materi el-type-i ssui ng-hei ght-dimen sion materi el-type-i ssui ng-len gth-dimen sion materi el-type-i ssui ng-wid th -d imens ion

bridge -typ e-desi gn-type-cod e

h arbour-type-i d (FK)

mi litary-p ost-ty pe-catego ry -code mi litary-p ost-ty pe-rank-cod e

can dida te -targe t-d etail-a ssoci ation-c ategory-cod e

provides-circumst ances-f or

ob ject-type-i d (FK)

CANDI DA TE-TARGET-DETAIL-IT EM candi date-target-li st-i d (FK) candi date-target-detai l-ind ex (FK)

is-specif ied-in / records-the-observed-result s-f or

o bjec t-typ e-category-co de o bjec t-typ e-dummy-in dica to r-co de o bjec t-typ e-name-text

obje ct-ty pe-catego ry -c ode

MATE RI EL-T YPE materi el-type-i d (FK)

BRIDGE-TYPE bridge -typ e-id (FK)

HARBOUR-TYPE

TASK-FORMATI ON-TYPE task-fo rma ti on-type -i d (FK)

actio n-context-status -c ategory-cod e actio n-context-status -e ffe ctive-da te ti me actio n-context-status -e stabli shi ng-organi satio n-id (FK )

CANDIDATE -T ARGET -DETA IL-TYPE

may-specif y

is-specif ied-as / is-a-designat o i n-f or

mil itary-obs ta cle-type -c ategory-co de

MILI TARY-POST-TYPE mi litary-p ost-ty pe-id (FK)

applies-to

a ction-reference-as soci ation-ca tegory-cod e a ction-reference-as soci ation-pa rt-text

is-ref erenced-t o

nucle ar-event- category-code

records-the-observed-result s-f or

requ est-id (FK )

military-organisation-type-category-code

action -e ffe ct-i tem-ratio obje ct-i tem-id (FK)

CA NDIDATE-TA RGET-DETAI L-A SSOCI ATION can dida te -targe t-d etail-a ssoci ation-s ubjec t-c andi date-target-lis t-i d (FK) can dida te -targe t-d etail-a ssoci ation-s ubjec t-c andi date-target-detail -inde x (FK) can dida te -targe t-d etail-a ssoci ation-o bject-ca ndid ate-ta rg et-l ist-id (FK) can dida te -targe t-d etail-a ssoci ation-o bject-ca ndid ate-ta rg et-d etail -i ndex (FK)

provides-applicable -inf ormat ion-f or / is-ref erenced-t o may-be-specif ie d-as /

si -specif ied-in /

requ est-category-co de requ est-immedi ate-interes t-i ndic ator-code requ est-latest-ans wer-datetime

wea pon-type-ca tegory-cod e wea pon-type-su bcateg ory-code wea pon-type-ca lib re -te xt wea pon-type-fire-gui dance -i ndi cator-code

a ction-effec t-type -c ount o bjec t-type -i d (FK)

is-the-subject -of is-t he-object-of

candidate-target-detail- category-code

actio n-id (FK ) contex t-i d (FK) actio n-context-in dex (FK) actio n-context-status -i ndex

may-be-specif ied-as /

is-relevant-f or

vehicl e-type-ca te gory-code

A CT ION-CONTEX T-STATUS

may-specif y

is-t he-load-in / specifies-the-stored-amount-of

VEHICLE-TYPE vehicl e-type-i d (FK)

applies-to

is-assigned / is-the-approval-for

can dida te -ta rg et-d etail -a uthorisa ti on-app roval -c ode can dida te -ta rg et-d etail -a uthorisa ti on-prio rity-ordin al repo rti ng-data-id (FK)

has / si -ascribed-to

ac tion-co ntext-category-co de

ACTI ON-RE FERENCE-AS SOCIA TION a ction-i d (FK) reference -i d (FK) a ction-reference-as soci ation-i ndex

provides-applicable-inf ormat ion-f or /

o bjec t-typ e-id

fa cil ity-type-cate gory-code

is -main-equipment-of / has-as-main-equipment

ca ndid ate-target-detail -category-c ode ca ndid ate-target-detail -focu s-ty pe-code ca ndid ate-target-detail -labe l-text ca ndid ate-target-detail -priority-ord inal ca ndid ate-target-detail -scheme -c ode

can dida te -ta rg et-l ist-id (FK) can dida te -ta rg et-d etail -i ndex (FK) can dida te -ta rg et-d etail -a uthorisa ti on-in dex

ACTION-CONTEXT ac tion-id (FK) co ntext-id (FK) ac tion-co ntext-inde x

CA PABILI TY-RE FERENCE-AS SOCI ATION cap abil ity-id (FK) refe re nce-id (FK)

provides-applicable -inf ormat ion-f or / is-ref erenced-t o is-the-reason-f or / is-based-on

OBJECT-TY PE

FACILIT Y-TYPE fa cil ity-type-id (FK)

h arbour-type-ca te gory-code

action -i d (FK) action -e ffe ct-i ndex (FK)

is-specif ied-as / is-a-designat ion-f or

is-used-as-specif ied-by

is-specif e i d-as / is-specif ci ation-of

is-specif ied-w ith / is-specif ied-f or

CANDI DAT E-TARGE T-DET AIL ca ndid ate-target-lis t-i d (FK) ca ndid ate-target-detail -inde x

CA NDIDATE -T ARGET -DETA IL-AUT HORISAT ION

identif ies-t he-source-for / is-ref erenced-to

ACTI ON-EFFE CT -I TEM

a ction-i d (FK) a ction-effec t-i ndex (FK)

ac ti on-task-s ta tu s-category-co de ac ti on-task-s ta tu s-compl etion-ratio ac ti on-task-s ta tu s-plan ning -i ndi cator-code ac ti on-task-s ta tu s-progress-co de ac ti on-task-s ta tu s-amend-timi ng-cod e repo rti ng-data-i d (FK)

acti on-task-ca te gory-code

is-ref erenced-to

is-specif ied-as / is-specif icat io n-of

is-specif ied-as-having / is-normal-quantity-stated-f or

mil itary-obs ta cle-type -i d (FK)

identif ies-t he-source-f or / is-ref erenced-to has-relevant -inf ormation-in

provides-applicable-in f ormation-for / is-ref erenced-to

cap abil ity-refe re nce-ass ocia ti on-categ ory-code

ACTION-T ASK-ST ATUS ac ti on-task-i d (FK) ac ti on-task-s ta tu s-inde x

has / is-ascribed-t o

is-authorit y-f or-t he-use-of / is-specif ied-as / is-specif ication-of

obje ct-typ e-capab ili ty-norm-missi on-prim acy-cod e obje ct-typ e-capab ili ty-norm-quanti ty

geo graphi c-featu re -typ e-category-c ode

ca ndid ate-ta rget-lis t-as soci ation-su bjec t-ca ndid ate-ta rg et-list-i d (FK) ca ndid ate-ta rget-lis t-as soci ation-ob ject-can dida te -targe t-l ist-id (FK)

candi date-target-li st-authoris ation-i ndic ator-c ode candi date-target-li st-authoris ation-pri ority-ordi nal re porting -d ata-id (FK )

is-referenced-t o

acti on-effect-catego ry-code acti on-effect-desc ri ption -c ode acti on-effect-severity-code reportin g-data-id (FK)

action -e ffe ct-c ategory-cod e

has-its-role-specif ied-through

target-perso nnel -protection -c ategory-cod e repo rti ng-data-id (FK) is-quant fi ied-in / quantif ies

OBJE CT-TY PE-CAPABI LI TY-NORM obje ct-typ e-id (FK) capab ili ty -id (FK )

MILITA RY -OBST ACLE-TY PE

ACTION-EF FECT acti on-id (FK) acti on-effect-ind ex

actio n-even t-de ta il-cl assi fi cation -c ode actio n-even t-de ta il-cri me-indi cator-cod e actio n-even t-de ta il-text reportin g-data-id (FK)

acti on-even t-sta tu s-compl etion-ratio reportin g-data-id (FK)

ACTI ON-EFFECT-TY PE

organi sation -a ction-a ssoci ation-c ategory-cod e organi sation -a ction-a ssoci ation-e ffec ti ve-da te ti me organi sation -a ction-a ssoci ation-i ntent-text

is-specif ied-as /

TARGET-PERSONNEL-PROT ECT ION

materie l-type-id (FK)

GEOGRAPHIC-FEATURE-TYPE geo graphi c-featu re -typ e-id (FK)

ACT ION-EV ENT -DETA IL actio n-even t-i d (FK) actio n-even t-de ta il-i ndex

ACTION-EV ENT -STATUS acti on-even t-i d (FK) acti on-even t-sta tu s-inde x

provides-applicable-in f ormation-for / is-ref erenced-to

ORGA NI SATI ON-ACTION-AS SOCI ATION organi sation -i d (FK) action -i d (FK) organi sation -a ction-a ssoci ation-i ndex

Z

action-objective-type-category-code STORA GE-CAPA BILITY storage -c apabi li ty -i d (FK)

P

cbrn-event-category-code

provides-applicable-inf ormation-f or /

a ction-ob jecti ve-item-marki ng-la ser-correla ti on-cod e-te xt a ction-ob jecti ve-item-marki ng-metho d-code a ction-ob jecti ve-item-marki ng-pan el-sh ape-cod e a ction-ob jecti ve-item-marki ng-reco gniti on-sig nal-co lour-cod e a ction-ob jecti ve-item-marki ng-start-datetime a ction-ob jecti ve-item-marki ng-usi ng-orga nisa ti on-id (FK)

is-recognised-as-having /

surveil lanc e-capab ili ty -category-co de

is-ascribed-to

cb rn-event-cate gory-code cb rn-event-sub catego ry -c ode cb rn-event-al arm-re sult-in dica to r-co de cb rn-event-con firmati on-test-ind icator-cod e cb rn-event-materi el-con ta iner-type-co de cb rn-event-materi el-con ta iner-total-co unt

ca ndid ate-ta rget-lis t-as soci ation-ca te gory-code

identif ies-the-source-f or /

is-detailed-through

has /

action-event-category-code CBRN-EVE NT cb rn-event-id (FK)

a ction-tas k-category-co de a ction-tas k-activi ty-code a ction-tas k-mini mum-duration a ction-tas k-estimated -d uration a ction-tas k-maximu m-d uration a ction-tas k-plan ned-start-datetime a ction-tas k-start-qu ali fie r-co de a ction-tas k-plan ned-end -d atetime a ction-tas k-end-qua lifier-cod e a ction-tas k-priority-co de a ction-tas k-entail ed-safety-degree -c ode a ction-tas k-overt-cove rt-cod e a ction-tas k-detail -te xt c andi date-target-li st-i d (FK) o rg anis ation-struc tu re -roo t-o rg anis ation-i d (FK) o rg anis ation-struc tu re -i ndex (FK)

CANDIDAT E-TARGET -LI ST-ASSOCIAT ION

CANDIDATE-TARGET-LIST-A UTHORI SATI ON candi date-target-li st-id (FK ) candi date-target-li st-authoris ation-i ndex

may-be-used-in-planning / planning-may-use

ACTI ON-EVENT a ction-event-id (FK)

ACTI ON-TASK a ction-tas k-id (FK )

actio n-obje ctive-i te m-c ategory-co de cand idate-target-li st-id (FK) cand idate-target-detai l-in dex (FK) obje ct-item-id (FK)

consist s-of / makes-up

is-assigned / is-the-approval-f or is-placed-within

is-measured-by /

action -c ategory-co de

i s-the-obj ective-for

A CTI ON-OBJECTI VE-ITE M actio n-id (FK ) actio n-obje ctive-i ndex (FK)

is-t he-subject-of is-the-object-of

c andi date-target-lis t-i d c andi date-target-lis t-n ame-text rep orti ng-data -i d (FK)

ac ti on-tempo ra l-asso ciati on-catego ry -c ode ac ti on-tempo ra l-asso ciati on-referen ce-duratio n

ac tion-fu nction al-ass ocia ti on-cate gory-code

records-observed-result s-of

SURVE ILLANCE-CAPAB ILITY surveil lanc e-capab ili ty -id (FK )

is-used-in-the-def init ion-of / is-def ined-wit h

ac tion-fu nction al-ass ocia ti on-sub ject-ac ti on-id (FK) ac tion-fu nction al-ass ocia ti on-obj ect-acti on-id (FK) ac tion-fu nction al-ass ocia ti on-in dex

is-act ed-upon-as-specif ied-by

a ction-event-catego ry -code

acti on-resource -typ e-quanti ty acti on-resource -typ e-apporti onment-ratio obj ect-type-id (FK)

mobi lity-ca pabil ity-cate gory-code mobi lity-ca pabil ity-terrain -typ e-code

is-used-in-the-def init ion-of / is-def ined-wit h

is-geomet rically-def ined-through

CANDI DAT E-TARGE T-LI ST ACTION-FUNCTIONAL-A SSOCI ATION is-the-subject-of is-the-object-of

is-f ocussed-on /

a ction-ob jecti ve-task-ac ti on-task-i d (FK)

acti on-obj ective-ty pe-catego ry-code acti on-obj ective-ty pe-quan ti ty can dida te -ta rg et-l ist-id (FK) can dida te -ta rg et-d etail -i ndex (FK) obj ect-type-i d (FK)

a ction-ai rcraft-empl oyment-ap proach-offse t-co de a ction-ai rcraft-empl oyment-de plane ment-method-co de a ction-ai rcraft-empl oyment-eg re ss-direc ti on-ang le a ction-ai rcraft-empl oyment-in fli ght-report-requi re ment-indi cator-cod e a ction-ai rcraft-empl oyment-in gress-di rection -a ngle

obj ect-item-i d (FK)

ACTI ON-OB JECTIVE -T ASK a ction-i d (FK) a ction-ob jecti ve-ind ex (FK )

ACTION-OBJECT IVE-TY PE acti on-id (FK) acti on-obj ective-inde x (FK)

ACTI ON-AIRCRAF T-EMPLOYMENT a ction-i d (FK) a ction-reso urce-ind ex (FK) a ction-reso urce-empl oyment-i ndex (FK)

ACTION-RESOURCE-IT EM acti on-id (FK) acti on-resou rc e-inde x (FK)

missi on-cap abil ity-categ ory-code missi on-cap abil ity-le vel-co de missi on-cap abil ity-qua lifier-cod e

is-f ocus-of

acti on-obj ective -c ategory-co de

actio n-resource -e mploy ment-category -c ode actio n-resource -e mploy ment-azimu th -fire-an gle actio n-resource -e mploy ment-method-of-control-co de actio n-obje ctive -i ndex (FK)

a ction-reso urce-empl oyment-ca te gory-code ac ti on-resou rc e-catego ry -c ode

MI SSI ON-CA PABI LI TY missi on-cap abil ity-id (FK)

acti on-catego ry -c ode acti on-name-text

action -o bjec ti ve-ca te gory-code action -o bjec ti ve-qu alifier-cod e action -o bjec ti ve-pri ority-code action -o bjec ti ve-au th orisi ng-organi satio n-id (FK )

ACT ION-RESOURCE-EMPLOYMENT actio n-id (FK) actio n-resource -i ndex (FK) actio n-resource -e mploy ment-inde x

o bjec t-i te m-c apabi li ty -mi ssi on-primac y-code o bjec t-i te m-c apabi li ty -q uantity rep orti ng-data-i d (FK)

eng inee ri ng-cap abil ity-id (FK) eng inee ri ng-cap abil ity-fa cili ty-heig ht-dimen sion eng inee ri ng-cap abil ity-fa cili ty-leng th -dimen sion eng inee ri ng-cap abil ity-fa cili ty-width-di mensi on fa cili ty-type-id (FK)

ACTION acti on-id

requires-as-a-minimum / is-minimum-required-f or

ACTI ON-OBJECTIV E action -i d (FK) action -o bjec ti ve-in dex

is-t he-subject-of / is-relevant-f or Z

ac ti on-resou rce-catego ry -c ode ac ti on-resou rce-critic ality -i ndic ator-code ac ti on-resou rce-qual ifi er-code ac ti on-resou rce-authori sing -o rg anis ation-i d (FK)

OBJECT-IT EM-CA PABI LI TY o bjec t-i te m-i d (FK) c apabi lity-i d (FK) o bjec t-i te m-c apabi li ty -i ndex

a mmuniti on-type-id (FK)

requires / is-required-f or

actio n-require d-capab ili ty -quanti ty

is-quantif ied-in / quantif ies

cap abil ity-categ ory-code

FI RE -CAPA BILITY fire-cap abil ity-id (FK)

ENGI NEE RI NG-CA PABI LI TY

absolute-point-category-code

trac k-area-left-w idth-di mensi on trac k-area-right-wi dth-dimen sion trac k-area-begi n-poi nt-id (FK ) trac k-area-end-p oint-id (FK)

is-def ined-using is-ending-point-f or / is-def ined-using

CARTES IAN-POI NT cartesia n-poin t-i d (FK) cartesia n-poin t-x -c oordin ate-dimen sion cartesia n-poin t-y -c oordin ate-dimen sion cartesia n-poin t-z -c oordin ate-dimen sion cartesia n-poin t-x -p re cisi on-cod e cartesia n-poin t-y -p re cisi on-cod e cartesia n-poin t-z -p re cisi on-cod e

GEOGRAPHIC-POINT g eograph ic-poi nt-id (FK ) g eograph ic-poi nt-latitud e-coordi nate g eograph ic-poi nt-long itude-co ordina te g eograph ic-poi nt-latitud e-precis ion-co de g eograph ic-poi nt-long itude-prec isi on-code

E LLIP SE ell ipse -i d (FK)

is-t he-centre-f or / has-as-its-centre is-the-f irst-conjugate-poin t -f or / has-as-it s-f irst-conjugat e-poin t is-the-second-conjugate-point-f or /

ell ipse -c entre-poin t-i d (FK) ell ipse -first-conj ugate-di ameter-poi nt-id (FK ) ell ipse -s econd -c onju gate-dia meter-poin t-i d (FK)

has-as-it s-second-conjugate-point

Syntactic Transformations

XML Schema Definition

FGAN

...

m m A R

V

A

P

D

A

A

P

Java Classes

D

A

P

m & R

m V

D

V

D

D V D

D

R

V

D

D

D

Research Institute for Communication, Information Processing and Ergonomics

KIE

Tool Support – XML Unmarshalling OI1 West Minefield … FR MinefieldLand • Stream-processing based on Simple API for XML (SAX) … oID = OI1 • Object creation/manipulation by Java reflection depthPlacementCode = MIXED YES functionCode = NUISNC • Validation of incoming XML instance documents … patternCode = REGTHK • Proves that XML documents can be handled efficiently persistenceCode = REMOTE … • Nesting of XML elements

XML Parser

XML Document

• Associative entities Java Objects • Supports incremental updates • No meta model information required ReportingDataAbsoluteTiming oID = RPTD005 effectiveStartDatetime = 20020102000000.000 effectiveEndDatetime = accuracyCode = …

FGAN

Research Institute for Communication, Information Processing and Ergonomics

FacilityStatus categoryCode = NOS demolitionStatusCode = enemyActivityConditionCode = minePresenceCode = YES, …

KIE

Findings „ Naming and Design Rules only partially suitable ‹ ‹

JC3IEDM follows its own naming conventions Contradictions between different NDRs

„ Standard XML Binding Frameworks ‹ ‹

Resolution of graph structures by XML’s ID/IDREF mechanism Incremental updates require a more flexible reference mechanism

„ W3C XML Schema ‹ ‹ ‹

Uniqueness & referential constraints by naming conventions Type model of XML Schema cannot be used Technically complicated solution, difficult to extend

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

WS/OO XSD – Products „

XML Design Specification ‹ Standardized as Annex O of the JC3IEDM 3.0

„

WS/OO Tool Set ‹ XML schema definition, XSD/Java generator, XML examples ‹ Generator written in Java 5 SE ‹ Eclipse 3.1 project ‹ Berkeley Software Distribution (BSD) license

„

Available on the MIP web site ¨ http://www.mip-site.org

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE

Summary „

MIP WS/OO XSD as a means to harmonize C2IS ‹ XML standard data elements derived from widely accepted data model ‹ Based on JC3IEDM semantics

„

Foundation for Web Services and SOAs ‹ Abstracts from ER-specific properties of the MIP IEDM ¨ Simplified integration into Non-MIP systems

„

Supports a broad scope of XML applications ‹ Various information exchange mechanisms ‹ Builds a bridge between message-based and replication-based communication

„

Future work ‹ Update to the next version of the JC3IEDM (End of 2006) ‹ Formal representation of business rules ‹ RDF and OWL representations

FGAN

Research Institute for Communication, Information Processing and Ergonomics

KIE