C.4. COI Services and Data Standards

C.4. COI Services and Data Standards

282. Interoperability standards for COI services will have to be determined based on commonly agreed Mission Threads such as Battlespace Awareness, Joint Fires, Joint ISR or Medical Evacuation.

Table C.9. General Data Format Standards

ID:Purpose	Standard	Implementation Guidance
1:General definition for the Representation of Dates and Times.	Mandatory: ISO 8601:2004 - Data elements and interchange formats - Information interchange - Representation of dates and times	Implementation of the W3C profile of ISO 8601:2004 (W3CDTF profile) is recommended.
2:General definition of letter codes for Geographical Entities	Country Codes (ISO/STANAG)	Whenever possible, the ISO alpha-3 (three-letter codes) as described in the relevant promulgated NATO STANAG should be used.
4:General definition of geospatial coverage areas in discovery metadata	Mandatory:World Geodetic System (WGS) 84, ISO 19115 and ISO 19136 (for point references)	ISO 19139 provides encoding guidance for ISO 19115

Table C.10. Battlespace Management Interoperability Protocols and Standards

ID:Service/Purpose	Standard	Implementation Guidance
1:Expressing digital geographic annotation and visualization on, two-dimensional maps and three dimensional globes	Mandatory: TIDE Transformational Baseline Vers. 3.0, Annex A: NATO Vector Graphics (NVG 1.5), ACT, December 2009. Emerging (2014) TIDE Transformational Baseline Vers. 4.0 - Annex N: NATO Vector Graphics (NVG) v2.0, ACT, February 2013.	NVG shall be used as the standard Protocol and Data Format for encoding and sharing of information layers NVG and KML are both XML based language schemas for expressing geographic annotations.
4: Exchange of digital Friendly Force Information such as positional tracking information between systems hosted on a Mission Network and mobile tactical systems	Mandatory: AC/322-D(2006)0066 Interim NATO Friendly Force Information (FFI) Standard for Interoperability of Force Tracking Systems (FFTS).	All positional information of friendly ground forces (e.g. ground forces of Troop Contributing Nations or commercial transport companies working in support of ISAF Forces) shall be as a minimum made available in a format that can be translated into the NFFI V1.3 format.
8:Military Symbology interoperability	Mandatory: STANAG 2019, Ed.5:2008, Joint SmbologyAPP-6(C) Recommended: MIL-STD-2525C, Common Warfighting Symbology, Nov 2008	Note that the different standards are not fully compatible with each other and may require mapping services.

ID:Service/Purpose

Standard

Implementation Guidance

1:Expressing digital geographic annotation and visualization on, two-dimensional maps and three dimensional globes

Mandatory:

TIDE Transformational Baseline Vers. 3.0, Annex A: NATO Vector Graphics (NVG 1.5), ACT, December 2009.

Emerging (2014)

TIDE Transformational Baseline Vers. 4.0 - Annex N: NATO Vector Graphics (NVG) v2.0, ACT, February 2013.

NVG shall be used as the standard Protocol and Data Format for encoding and sharing of information layers

NVG and KML are both XML based language schemas for expressing geographic annotations.

4: Exchange of digital Friendly Force Information such as positional tracking information between systems hosted on a Mission Network and mobile tactical systems

Mandatory:

AC/322-D(2006)0066 Interim NATO Friendly Force Information (FFI) Standard for Interoperability of Force Tracking Systems (FFTS).

All positional information of friendly ground forces (e.g. ground forces of Troop Contributing Nations or commercial transport companies working in support of ISAF Forces) shall be as a minimum made available in a format that can be translated into the NFFI V1.3 format.

8:Military Symbology interoperability

Mandatory:

STANAG 2019, Ed.5:2008, Joint SmbologyAPP-6(C)

Recommended:

MIL-STD-2525C, Common Warfighting Symbology, Nov 2008

Note that the different standards are not fully compatible with each other and may require mapping services.