1 / 15

Universal Core Overview

Universal Core Overview. June 2007. Constructing a universal core data schema that enables information sharing Ways to describe “when, where, what” Minimal set of terms in the core Agreed to by DoD and Intel Community Appropriate use of open and Federal standards

Download Presentation

Universal Core Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Universal CoreOverview June 2007 UNCLASSIFIED

  2. Constructing a universal core data schema that enables information sharing Ways to describe “when, where, what” Minimal set of terms in the core Agreed to by DoD and Intel Community Appropriate use of open and Federal standards Extensible by COIs and systems as needed Extensible by COIs and systems as needed Strike Spiral 1 pilot is based on initial C2 common core (e.g., Task/Mission) Incorporates universal core DoD Component and IC Member Extensions COI Extensions Log Common Core ** C2 Common Core ISR Common Core ** Universal Core EIE Common Core ** Financial Common Core ** DoD and IC Universal Core Data Schema ** With the exception of the C2 Common Core, the other Common Core’s are notional Increased Data Interoperability AND Agility UNCLASSIFIED 2

  3. Start with just the most common Typical approach: Add new information for each new system exchange... Model continues to get larger and larger and difficult to manage Two systems, much info less is common One system, info intersection is everything Three systems, Intersection gets smaller Universal Core starts here with a core set of common info! UNCLASSIFIED

  4. Identified “data nuggets” that represent common data concepts* Position (10199 candidate elements – 10.3%) Quantity (10035 candidate elements – 10.1%) Shape (7241 candidate elements – 7.3%) Time (14161 candidate elements – 14.3%) Type (15444 candidate elements – 15.6%) Mining the XML Registry for Common Elements * From late 2005 - believe percentages are still valid UNCLASSIFIED

  5. Universal Core Background • DoD Directive 8320.1 • Attempted to define a large data model for all DoD systems to adopt • Too difficult to harmonize, implement, and scale • DoD Directive 8320.2 • Define and implement interoperability around Communities of Interest • Success harmonizing across the community and streamlining implementation • Cursor on Target • Simple, small, and powerful exchange standard • Applied loose coupling strategy • Led to numerous implementations and real warfighter capabilities • Universal Core • Leverages the harmonization success of Communities of Interest • Simplicity and power of Cursor on Target • Application of commercial and DoD/IC standards UNCLASSIFIED

  6. Universal Core Key Principles • Key Principles • Build a strong foundation • Policy, Governance, Definition, and Test processes • Build Joint from the start • DOD and IC communities • Harmonize across communities • Standards based • Small core with the following attributes • Suitability - include only a few critical objects • Simplicity - for widespread adoption • Extensibility - to meet individual community needs • Leveragability - of existing standards, tools, and expertise • Supportability - for long-term success UNCLASSIFIED

  7. Governance Process – Senior Enterprise Services Governance Group (SESGG) • Oversee Joint Data Strategy and Enterprise Services Implementation • Define the required measurement and control mechanisms to ensure DoD-wide and IC-wide implementation • Identify and develop necessary policy changes, including measurement and control responsibilities, to ensure consistent implementation • Establish oversight forums, as required, to enable the DoD CIO and DNI CIO to review implementation progress UNCLASSIFIED

  8. SESGG Members Mr. Mike Krieger, co-chair, DoD CIO Mr. John Brantley, co-chair, ADNI CIO Mr. Ron Bechtold, Army, Mr. Brian Clingerman, Navy, Mr. Kent Werner, AF Mr. David Green, USMC Ms. Bobbie Stempley, DISA Mr. Mac Townsend, DIA Mr. Dennis Wisnosky, BTA UNCLASSIFIED

  9. Universal Core Harmonization, Governance, Policy, Test • Four Working Groups, each containing participation from all the organizations that make up the SESGG • DNI and Navy lead the methodology for describing and evolving the universal core schema • AF leads the development of Governance processes • JFCOM and Army lead the Test and Evaluation methodology • DIA and DoD lead the Policy definition UNCLASSIFIED

  10. Standards-based Approach • GML 3.2.1 (ISO-19136) based on the ISO-19100 series • ISO-19103 – Conceptual Schema Language • ISO-19107 – Spatial schema (geometry and topology objects) • ISO-19108 – Temporal schema (temporal geometry, topology, temporal reference systems) • ISO-19109 – Rules for application schemas • ISO-19111 – Spatial referencing by coordinates (coordinate reference systems) • ISO-19123 – Schema for coverage geometry and functions • Key XML standards • W3C XML Schema • W3C XLink • Security Tagging • IC-ISM (Intel Community - Info Security Marking) UNCLASSIFIED

  11. GML Profile- Logical Subset of GML Standard GML ProfileLogical Subset of GML Data Types/Subset of gml:elements/attributes 11

  12. Security Marking – IC ISM Identification – gml:feature gml:id gml:name & gml:description Time & Geo Bounding gml:boundedBy Object Type – cc:type encoded via gml:dictionary Operational Info Association – cc:link (xlink) Universal Core – What, When, Where 12

  13. “High” Situational Awareness Info Security Marking – IC-ISM • Approach • IC ISM tagging • Required classification, ownerProducer • Other optional attributes • Structure document to support “tear-lines” “Low” Releasable SA Cross Domain Guard 13

  14. Generic linking to other documents To other Universal Core-based schemas To other non-Universal Core-based schemas Utilize W3C xlink standards Utilize locator link xlink:type – “locator” Xlink:href – link to object Xlink:role – meaning of link Xlink:title – (String) Description of associations Xlink:label – (String) – label for referenced object element property (xs:string) – used to describe the hierarchical type code of referenced object <uc:link xlink:href="http://www.aoc.mil/missionXYZ" xlink:role="OBJ.TASK.PRIMARY“ xlink:title="Primary Mission" \> Resource Linking 14

  15. Dictionary – structure to define terms/vocabulary contains dictionaryEntries where each dictionaryEntry has a definition gml:Definition identifier – unique identifier of the term name – synonyms for the term being defined description – textual definition of the term descriptionReference – link to definition of term remarks – additional clarifying comments about the term Dictionary UNCLASSIFIED

More Related