Unclassified

Unclassified
1
C2 Core Technical Overview

Level II




Joint Staff J8 Data and Services Division

Dec 2011
Unclassified
Unclassified
2
Level II Training Objectives

Review level I objectives
State the purpose of each of the C2 Core specifications
State the four phases of the IES development: Inputs, IES design time, IES
implementation time, runtime
State the purpose and list the artifacts created during IES design time
State the purpose of the IES implementation time phase
Explain the flow of a Payload-Only IEP from data producer to data consumer
Explain the flow of a UCore-Full IEP from data producer to data consumer
State the six steps of the IES development process
State the input, process and outputs of the Scenario Planning step
State the input, process and outputs of the Build COI/POR data model step
State the input, process and outputs of the Map to C2 Core step
State the input, process and outputs of the Build and Validate step
State the input, process and outputs of the Assemble and Document step
State the input, process and outputs of the Publish and Implement step
State where further C2 Core resources may be found
Unclassified
Unclassified
3
- Concepts Review
- Patterns of Implementation
- Documentation Review
- IES Development




Contents

Unclassified
Unclassified
4
C2 Core

Concepts Review


Unclassified
Unclassified
5
What is C2 Core?
[ Definition: C2 Core ]
Command and Control (C2) Core is an emerging, open standard
for eXtensible Markup Language (XML) based information
exchange, built for the C2 community by the C2 community.
Unclassified
Unclassified
6
C2 Core
Standard architectural framework
Leverages Universal Lexical Exchange
(ULEX) message envelope
Simplifies and standardizes Schema
representation
Reusable XML Schema components
Provides reuseable Schema components
representing all C2 Core vocabulary
Can be composed as needed into
specifications for particular data exchanges
Vocabulary and data model
Extends the Universal Core (UCore) vocabulary
Represents the semantic overlap among C2 Communities of Interest
(COIs) and Programs of Record (POR)
Unclassified
Unclassified
7
IES
Information Exchange Specification
[ Definition: IES ]
Information Exchange Specification (IES)
Packaged as self-contained, self-describing zip file
Artifacts include XML Schemas, instances, business rules,
documentation, etc. necessary to describe an implementable
exchange
Metadata file for search/discovery
Unclassified
Unclassified
8
Purpose of an IES
Establish requirements for building C2 Core-conformant
exchanges.
Document artifacts to meet the varied information needs of all
project stakeholders.
Establish process for synthesizing COI/POR business knowledge
from SMEs.
Enable artifact reuse across projects.
Leverage open industry standards.
Enable use of industry standards-based tools.
Share valuable lessons learned and best practices.
Unclassified
Unclassified
9
Information Exchange Package
[ Definition: IEP ]
Information Exchange Package (IEP)
XML document exchanged by partners in a C2 Core-conformant
information exchange
Encapsulates information being exchanged
Content is defined by an associated IES
IES IEP
defines
Unclassified
Unclassified
10
ULEX/UCore

XML Messaging Framework
Vocabulary of most commonly
exchanged concepts of who, what,
when, and where

XML representation

Extension rules allow tailoring to specific
mission areas

Security markings to control access,
electronic tear lines, etc.

Universal Lexical Exchange (ULEX)
messaging framework to package and
unpackage content consistently
For more information: https://lexs.gov/ and https://www.ucore.gov/
Unclassified
Unclassified
11
C2 Core: UCore Extension

C2 Core framework builds upon
the ULEX/UCore messaging
framework
Prescribes normative
specifications for implementing
the structured payload extensions
to UCore
Provides Naming & Design Rules
for standard implementation of
XML
Contains specifications for
documenting Information
Exchange Specifications (IES) for
registry in the DoD MDR
Unclassified
Unclassified
12
Peak Under the Hood
Reusable Schema component:
AirspaceCoordinatingMeasureType

Unclassified
Unclassified
13
Peak Under the Hood
Represents SME
agreement on data
definition
Clear and precise
semantics
Unclassified
Unclassified
14
Peak Under the Hood
C2 Core structural framework
provides IC-ISM, metadata,
id/idref and more
Unclassified
Unclassified
15
Peak Under the Hood
Customizable properties
Unclassified
Unclassified
16
C2 Core Patterns of Implementation
Unclassified
Unclassified
17
Fully UCore conformant; contains a UCore digest

Reuses C2 Core components in the Structured
Payload, optionally adds COI extensions
Implementation Pattern: UCore-Full
Unclassified
Unclassified
18
Implementation Pattern: Payload-Only
Use of C2 Core and
COI extensions
identical to UCore Full

Only the Structured
Payload is transmitted;
ULEX and UCore
portions omitted
Unclassified
Unclassified
19
UCore Conformance
UCore conformance is accomplished through implementation
of the UCore Full pattern or translation of the Payload Only to
UCore Full.
Option 1 Option 2
UCore
Transformer
Support for Option 2 is available directly from the Lead Developer
Unclassified
Unclassified
20
C2 Core Documentation
Material for this section is being migrated to the C2CDSN at URL:
https://c2core.gtri.org/wiki/Specifications
Unclassified
Unclassified
21
Concept of Development
Presents introduction to the following
C2 Core concepts:
Approach
Scope
Architectural framework
Lifecycle management concepts
Governance participants and roles
Unclassified
Unclassified
22
C2 Core FAQ
Answers common C2 community
questions

Examples:
What is the problem statement and value
proposition for C2 Core?
How does C2 Core align with Universal
Core (UCore)?
Unclassified
Unclassified
23
Conformance Specification
Defines high-level conformance
targets:
ULEX
UCore
C2 Core
IES
IEP
Specifies relationships between
artifacts and normative documents

Unclassified
Unclassified
24
IES Conformance Specification
Defines IES Schema Artifacts

Lists additional IES Artifacts
Documentation
Samples
Optional artifacts

Specifies Directory Organization and
Zip-file Packaging

Unclassified
Unclassified
25
Naming and Design Rules (NDR)
Outlines C2 Core data model including:
Reusable data components
Naming rules

Specifies Schema rules
Renders data components as type, element
and attribute definitions
Unclassified
Unclassified
26
NDR Conformance Targets
Defines Schema-level conformance
targets

Reference Schema
The set of ALL C2 Core reusable components
Subset Schema
The subset of only the C2 Core reusable
components necessary for a particular IES
Extension Schema
New or extended COI/POR reusable components
Exchange Schema
Declares the message envelope or wrapper
XML Instance
The Information Exchange Package (IEP)
Unclassified
Unclassified
27
Code List Specification
Optional specification

Provides Genericode solution for complex
code list problems, such as:
State-City problem
Type-SubType problem

Augments C2 Core NDR conformance rules
for Schemas code lists and Genericode
artifacts
Experimental Product
Unclassified
Unclassified
28
IES Development
Material for this section was migrated to the C2CDSN at URL:
https://c2core.gtri.org/wiki/Tutorial
Unclassified
Unclassified
29
END
29