Purpose | Standard | Guidance |
---|---|---|
General formatted message exchange | STANAG 5500 Ed.6:2009
AdatP-3 - Concept of NATO Message Text Formatting System (CONFORMETS) - ADatP-3(A) |
Use for exchanging information with existing systems that process
MTF messages.
Any addition or expansion of MTF messages or data dictionaries shall be developed in XML-MTF (9-liner MEDEVAC request, 15 -liner, SALTA reports etc.). All those extensions shall be submitted as a change proposal within the configuration control process to be considered for inclusion in the next version of the specification. |
Automated information resource discover, information extraction and interchange of metadata | ISAF Minimum Metadata Implementation Policy, ISO 15836:2009
also known as the Dublin Core Metadata Element Set
TIDE Information Discovery (v2.3.0, Oct 2009) TIDE Service Discovery (v.2.2.0 Oct 2008) Emerging (by Dec 2012): OpenSearch 1.1 Draft 4 |
The policy defines a subset of the NATO Discovery Metadata
Specification (NDMS) intended for information resource discovery.
ISO 15836:2009 does not define implementation detail. The technical implementation specifications are part of the TIDE Transformational Baseline v3.0. The TIDE community is evaluating OpenSearch for potential inclusion into the TIDE Information Discovery specifications. |
General definition for the Representation of Dates and Times. | ISO 8601:2004, Representation of Dates and Times. | If not otherwise specified, this format shall be used for representing Dates and Time values. |
General definition of letter codes for Geographical Entities | STANAG 1059, Letter Codes for Geographical Entities (9th edition, 2005) | Whenever possible, the ISO-3166 three-letter codes contained in STANAG 1059 should be used |
General definition of geospatial coverage areas in discovery metadata | World Geodetic System (WGS) 84, ISO 19115 and ISO 19136 (for point references) | ISO 19139 provides encoding guidance for ISO 19115 |
General definition of Security and Confidentiality metadata | Community Security Requirements Statement For The Afghan Mission
Network, Version 1.1, 2 June 2010.
(See also ISAF Minimum Metadata Implementation Policy, Amendment A: Metadata Encoding Guidance for the ISAF Minimum Metadata Standard and STANAG 1059 (9th edition, 2005) |
All system and programme managers have to plan to implement these new standards in their individual area of responsibility. See NATO Profile for the XML Confidentiality Label Syntax and NATO Profile for the Binding of Metadata to Data Objects for implementation detail. |
Sharing of information across Communities of Interest and across Security Domains with Object Level Protection | Emerging (Dec 2012): XML Confidentiality Label Syntax Version 1.0
of the RTG-031 proposed XML Confidentiality Label Syntax (FFI Publication).
NATO Profile for the XML Confidentiality Label Syntax (NC3A RD-2903). Binding of Metadata to Data Objects Version 1.0 of the RTG-031 proposed Binding of Metadata to Data Objects (FFI Publication). NATO Profile for the Binding of Metadata to Data Objects (NC3A RD-2977). |
Emerging: The XML-Labeling and Binding specifications are published
as annexes to the final report of RTO Task Group IST-068/RTG-031 on
"XML in Cross-Domain Security Solutions". They are also available as
separate publication by the Norwegian Forsvarets forskningsinstitutt
(FFI)
For use within NATO specific NATO profiles of these specifications must be used. These are available as NC3A Reference Documents |
Asset/ consignment tracking | The following two STANAGS require updating to reflect the IERs
identified in ISAF CUR 254.
STANAG 2185 STANAG 2183 |
Use for exchanging information with existing systems that process
Asset and Consignment information.
Note that their evolution is foreseen to also regulate the civilian convoy information exchange |
Table D.4. COI Interoperability