DoD Metadata Registry Status

1. DoD Metadata RegistryStatus Dr. Glenda Hayes NCES Data Advisor May 17, 2006 UNCLASSIFIED

2. Agenda • DoD Net-Centric Data Strategy • Data Strategy Implementation Actions • Role for NCES Enablers • DoD Metadata Registry

3. DoD Net-Centric Data Strategy The DoD Net-Centric Data Strategy is the plan to make the Department’s information resources: Is an information resource discoverable by most users? Visible Is it available on the network, and are tools readily available to use it? Accessible Understandable Can it be intelligibly used? Are the semantics well documented? Trusted Is the source, accuracy and currency of the data available to users? Can it be combined or compared with other information? Can it be mediated? Interoperable Is the data what users need? Are robust user feedback mechanisms in place to improve it? Responsive CC/S/As must institutionalize processes to accomplish these goals

4. Data Strategy Goals& Actions Required Visible Responsive Accessible Understandable Trusted Interoperable Visible Data Asset Sponsors, Builders, and Operators: Specific Actions Required Implement DOD Data Strategy per Directive 8320.2 • Identify System Assets to Expose • Determine Tagging Method & Technologies • Maintain Catalogs • Tag & Post Asset Info • Register/Publish Metadata • Identify Assets for Access • Select Applications • Provide Data Access Services • Post Assets • Register Service • Select/Create Taxonomy & Vocabulary • Develop Information Model & Register • Develop data Payload packages & Register • Provide Access • Usage Controls • Manage Rights • Publish Data Asset Pedigree & Authoritative Source Designs • Register Metadata • Define & register Metadata Relationships • Identify Key System Interfaces • Comply with Net-Centric Interface Specs • Create & Monitor Robust Feedback Mechanisms • Closely link Development & Ops • NCES enables via online services, interface specs and Software Development Kits

5. Enable Data To Be Understandable One reason Government Agencies and Military Services have trouble operating jointly is that they speak different languages. “Secure the Building!” What does it mean? • Navy: “Turn off the lights and lock the doors.” • Army: “Surround the building, occupy, and control entry.” • Marines: “Call in close air support, assault with small team, neutralize occupants, fortify and hold at all costs until properly relieved. SEMPER FI!” and… • Air Force: “Take out a three-year lease with option to buy.” Register Terms, Definitions, & Relationships

6. Interoperability Requires: Physical Identity or Translation/Transformation Translate/Transform via neutral “mediation” schema (to reduce “n-squared” point-to-point interface problem) Support Data Interoperability F-14 F-14 Etc. Tomcat F14 F/14 Interoperable data thru “sameness” Interoperable thru translation via neutral schema Interoperable “pair-wise” but inefficient Register Data Translations

7. DoD Metadata Registry(MDR) and Clearing House • “One Stop” Publish, Subscribe and Manage capabilities for Reusable Structural Metadata Components • 130k engineering artifacts (schema, stylesheet etc) registered as of 5/16 • Includes translation logic for mediation & taxonomies • 7k Registered Users & Systems from DoD, IC, DHS, NASA and more • Unclassified, Secret and Top Secret instances operating • Organized by “Gallery” • Metrics • Run Time support available • Web Services • ebXML capabilities • User feedback driven • Online user-to-developer • DoD Metadata Working Group • V5 just released http://metadata.dod.mil

8. Unclassified (Open) NIPRNET w/Internet Access http://metadata.dod.mil Unclassified (Sensitive) Open Registry contents plus “password protected” components NIPRNET with Internet Access http://metadata.dod.mil Secret Unclassified (Sensitive) content plus secret components SIPRNET http://diides.ncr.disa.smil.mil Top Secret (SCI)  Managed by ICMWG Secret content plus SCI components JWICS MDR Accessibility Users Discover and Pull metadata they are cleared for - Top Secret (SCI) Secret Unclassified (Sensitive) Unclassified (Open) Engineering Components replicated from lower to higher security enclaves Synchronized Components on Multiple Networks

9. MDR Support for Mediation Legend • Convert XML to XML • Report status (degree of success/failure) schema stylesheet sample 2004-ATO.xsd (schema) TransformsToXmlSchema HasXSLT notional 2005-2004-ATO.xsl (stylesheet) 2004-2005-ATO.xsl (stylesheet) HasXSLT TransformsToXmlSchema 2005-ATO.xsd (schema) XML Gallery Organizes Components for Mediation 2005-ATO.xml (sample) DescribedBy Registered in DoD Metadata Registry

10. Mediation Use Case NCES MEDIATION Common Message Processor APIs transform USMTF text message into XML format CMP Message Feed Mediation listener XSLT stylesheet used to translate from USMTF schema to KML schema is retrieved from DoD Metadata Registry Transformation is applied to create KML file. The result is returned to the client or stored on the Global Information Grid Client NCES Mediation ServiceStandards-based WS-I Basic Profile compliant web service to transform USMTF message to KML Network links in Google Earth access the kml files and update positional information

11. NCES Enabler:Service Oriented Architecture Foundation Register Db Structure DoD Metadata Registry* What structures are available for reuse? Web Interface ATO Service 1* e.g. ATO access service What services are available for reuse NCES Service Registry* ISR Task List Service 2* Developer Web Interface e.g. Sensor Tasking Service Where are services available for my users? Use Service 3* DDMS DDMS e.g. Content Discovery DDMS User • Register structural metadata • Develop & register web services • Develop applications Register I/O Structure Register operations Application * NCES Security Service Warfighter, Intelligence, & Business User benefit indirectly

12. Using Discovered Content Federated Search* Defense Knowledge Online* Data Collection “Pull the data” Federated Search* This database has data you are looking for <IFF>F</IFF> Information System What does “F” Mean? Pull meaning, structure, & constraints Federated Search* DoD MDR With access to the data source and the associated metadata, the user/application can make informed use of the data. Database

13. MDR Support for Taxonomies DoD Core taxonomy Organization PoliticalOrganization UrCOI taxonomy MyCOI taxonomy Group TerroristOrganization equals ForeignTerroristOrganization TerroristGroup equals al-Qaeda AlQaida Consumer View Producer View <ddms> : <Subject>…/MyCOI.owl#AlQaida</Subject> </ddms>

14. www.disa.mil

15. NCES Enabler:Content Discovery Search Web Service enables federated content searches Federated Search* Defense Knowledge Online* Data Collection Application (machine-to-machine) Federated Search* DoD MDR Service Registry Information System Other Portal (e.g. Intellink-S) Supporting roles Federated Search* * NCES Security Service Database Defense Knowledge Online is one way to use Content Discovery

16. Making Data Visible (1 of 2) DoD Discovery Metadata Specification (DDMS) * * * * * Data Catalog (historical) DDMS endorsed by Executive Order 13388 * “Further Strengthening The Sharing Of Terrorism Information To Protect Americans” * mandatory DDMS: Leverages Industry Standard

17. Make Data Visible (2 of 2) • Approach • Publish resource metadata (IAW DDMS) • Query & federate via NCES Discovery Services • Applies to… • Documents – Publish resource metadata (DDMS) in Data Catalog(s) • Services • Register web service operations in NCES Service Registry • Register I/O structures in DoD Metadata Registry Unanticipated consumer Enterprise Search Federated Search Federated Search Federated Search Federated Search DDMS Sharepoint COI Data Catalog Operational DB Content Mgmt Solution Federated Search Leverages Operational Catalogs

18. Leverage Registered Domain Sets by Linking To Core DoD Core Taxonomy MSG Ordnance Type (752) INT Mission Type (476) GMI FPA (38) GMI INCIDENT (241) GOP Ship Type (1339) MSG Aircraft Type (2889) GMI Political Subdivision (3784)