Title
ISR Library Interface Profile
Description
The ISR Library Interface is the standard interface for querying and accessing heterogeneous product libraries maintained by various nations.

Reference document

Org
FMN
Pubnum
Date
2022-12-02
Version
Title
Proposed FMN Spiral 5 Specification

Taxonomy

Standards

Obligation: MANDATORY, Lifecycle: CANDIDATE

The following NATO standards provide the specification as well as business rules for interoperability of ISR libraries.

Obligation: MANDATORY, Lifecycle: CANDIDATE

The following NATO standards are mandated for interoperability of ISR library products.

Obligation: MANDATORY, Lifecycle: CANDIDATE

The Basic Image Interchange Format (BIIF) is mandated for interoperability of ISR libraries.

Obligation: MANDATORY, Lifecycle: CANDIDATE

The following international standards are mandated for interoperability of ISR libraries.

Obligation: MANDATORY, Lifecycle: CANDIDATE

Implementation of JC3IEDM (STANAG 5525) in the context of the ISR Library Interface Profile is limited to the definition of unique keys that could be used to unambiguously refer to an external information object that is modelled in accordance with JC3IEDM. Note that AEDP-17 refers to the metadata attribute “JC3IEDMIdentifier” on page G-15, but to “identifierJC3IEDM” on page G-79. The correct attribute to use is “identifierJC3IEDM”.

Guidance

To ensure optimization of network resources the ISR Library Interface services work best with a unicast address space.

AEDP-17 defines four interfaces

  • STANAG 4559CORBA’sinterface,
  • provider-consumer interface (seeISR Library Access Pattern) based on HTTP/HTTPS interface'
  • CSD-Publish services interface,
  • CSD-Query services interface.

The CORBA interface is required for server to server interaction (i.e., federation) as well as client to server interaction.

The HTTP/HTTPS interface is for transferring files between server and clients as well as remote file access.

The Publish and Query are web service interfaces supporting only client to server interaction. Although AEDP-17 allows for the use of partially qualified attribute name for the queries (see AEDP-17 section B-3.10.3 Query validation), the use of fully qualified attribute names are recommended since some AEDP-17 implementations require such fully qualified attribute name and this will ensure an adequate mapping to the right attribute. This is particular important considering the extension required to support all information products specified within the FMN Spiral 4 Procedural Instructions for Intelligence and JISR.

AEDP-17 Annex K provides further details on the ISR Library synchronization.

Service provider must identify which interfaces/patterns they support as a part of the federation process.

Status

URI

History

Flag Date RFC Version
added 2023-01-23 14-32 15
UUID
0851db1a-291e-4f89-8ebc-43e600424dd5

Utilization

This profile is used by the following profiles: