Semantic Interoperability Honoured Guest or Orphan at the Feast

1
Semantic InteroperabilityHonoured Guest or
Orphan at the Feast?
6th NATO CIS Symposium
Staff

• Mr Peter Pharaoh
• Staff Officer, NATO HQ C3 Staff
• (p.pharaoh_at_hq.nato.int)

2
Why pay attention?

• Homonyms can kill..unintentionally

3
OVERVIEW
Staff

• A Real world example of the homonym issue
• NATO Data Management
• Metadata and Semantic Interoperability explained
• NC3B main initiatives in this field.

4
Nation A Sensor
Friendly Forces
5
Nation B Shooters
Adversary forces
Nation B C2 system
6
NATO Data Management
Staff

• Development, approval, use/reuse, and
  maintenance of data standards for NATO which
  provide semantic interoperability at the data
  level
• Plan, organise and control meta data which
  delivers basic rules and standard data elements
  (including definitions) to NATO bodies, agencies,
  Common Funded projects and is offered to national
  projects/programs

Data Administration for precise definition of
terms
JC3IEDM produced in collaboration with the
Multilateral Interoperability Programme (MIP)
7
Data in Context
Staff

• 74, F, 8AU7, 432,741,24160424Z
• 74, F, 8AU7, 432,741,24160424Z

A Data string, no context
Target ID
Date-time Group
Data in context
Target Affiliation
Map overlay grid reference
8
NATO DATA MANAGEMENT Semantic Interoperability
2 Components
Agreed Terms or Data Elements
Agreed Method of Exchanging the Terms Reliably
9
The Product- Aluminium Can- Drinks Liquid
NATO DATA MANAGEMENT Meta-Data
Staff
Meta-DataLabel Information - Product Name-
Batch Number- Contents- Weight/Volume-
Manufacturer
10
NATO DATA MANAGEMENT Semantic Interoperability
How we are doing this part 1
Agreed Method of Exchanging the Terms Reliably
11
Data Administration

• Delivers semantic interoperability at the data
  level-- a key enabler to NNEC
• Enhances system interoperability, integration and
  integrity by meta data standardisation
• Establishes a single authoritative source for
  Standard Data Elements (SDE)
• Is independent of any particular modelling method
  
• Enables meta data reuse across project boundaries
• Maintains SDEs under configuration control
  throughout their life-cycle

12
XML Registry

• MOU established in September 2006
• Use of USA facility
• Standard Data Element storage
• 4 Name-spaces established
• NATO Data Administration
• Message Text Formats
• Tactical Data Links
• Op Intel
• Planned to be operational in early 2007.

13
NATO DATA MANAGEMENT Semantic Interoperability
How we are doing this part 2
Agreed Terms or Data Elements
14
Multilateral Interoperability Programme
Staff

• 11 Full Member Nations
• 15 Associate Members
• 16 Nations have implemented the C2IEDM/JC3IEDM as
  a basis for their national information systems
• MIP-NATO MOA established
• STANAG 5525 covers the JC3IEDM ratification in
  process.

15
Multilateral Interoperability Programme the
JC3IEDM
Staff

• Land-based Command and Control
• 98 of the Air Tasking Order implemented
• Maritime Mine Warfare
• All Chemical, Biological, Radiological and
  Nuclear (CBRN) elements incorporated
• 15 additional Air, Maritime and Joint messages
  approved for incorporation by end 2007.

16
Summary

• killer homonyms
• NATO Data Management
• Metadata and semantic interoperability
• NATO C3 Board initiatives
• Data Administration (XML Registry)
• Collaboration with MIP the JC3IEDM.

17
NATO Network Enabled Capability
Data Definitions Data Structures Data Sharing
Semantic Interoperability
JC3IEDM
JC3IEDM is a Key Enabler for Semantic
Interoperability
18
Questions?
19
Backup slides
20
NATO Data Management
Staff

• Provides direction for the development,
  approval, use, reuse and maintenance of data
  standards for NATO, which will provide semantic
  interoperability at the data level
• Embraces the planning, organisation and control
  of meta data which delivers basic rules and
  standardised data elements (including
  definitions) to NATO bodies, agencies, Common
  Funded projects and offered to national projects
  and programmes.

21
Namespace Managers Tasks

• Responsible for the development and maintenance
  of the namespace
• Focal point of contact for all matters pertinent
  to the namespace
• Harmonise their XML components with other
  namespaces