310 likes | 338 Views
DoD Metadata WG. Dr. Glenda Hayes NCES Data Advisor Glenda.Hayes.ctr@disa.mil 8 Dec 2005. DoD Net-Centric Data Strategy Goals. Make the Department’s Data:. Is an information resource and associated POC discoverable by most users?. Visible.
E N D
DoD Metadata WG Dr. Glenda Hayes NCES Data Advisor Glenda.Hayes.ctr@disa.mil 8 Dec 2005
DoD Net-Centric Data Strategy Goals Make the Department’s Data: Is an information resource and associated POC discoverable by most users? Visible Is it connected to the network(s), and are tools readily available to use it? Accessible Can it be intelligibly used? Are the semantics well documented? Understandable Is the source, accuracy and currency of the resource available to users? Trusted Can it be easily combined or compared with other information or mediated? Interoperable Is the resource answering user needs? Are robust, direct user feedback mechanisms in place to guide development? Responsive
Differentiating Types of Metadata • Structural Metadata • “Rules governing a chunk” - Name, description, data constraints, and relationships of tags used in information resources to delimit one chunk of data from another chunk • Artifacts where structural metadata is described: XML schemas, RDBMS structures, taxonomies • Register in DoD Metadata Registry, use submission pkg • Resource Metadata • “Advertisement” - Terms to aid in the recall and retrieval of artifacts • Artifacts that we collect resource metadata on: PPT, DOC, GIF, JPG, MPG, RDBMS • Register in “Data Catalog”, use DDMS bibliographic information
Working Group Relationships IIPT GES Data Strategy WGChair: NII COI ForumCh: NII NCES Eng WIPT DoD Metadata WGChair: NE SOAF WG Metadata Registry FG Service Mgmt CES Metadata FG Focus Area A Security Service DoD Core Taxonomy FG equals Identity Mgmt DDMS FG Metadata Services TBD FG Focus Area B Mediation M2M Messaging Defense Online Portal WG Pilot WG DOD Enterprise Collaboration WG Architecture WG Content Discovery & Delivery WG
DoD Metadata RegistryEngineering-level Processes Participates in Data Working Group DISA Engineering Staff DoD Metadata WG ICMWG Reports to Hosts DHS MCOE MDR FG Operates, Reports to Develop & Publish Maintains Participate in CES FG Governs/Coordinates Acts as Registry CM Board Namespace Managers & WGs Namespace Managers & WGs Namespace Managers & WGs DoD Metadata Registry Participates in Registry Ops Staff Controls/Displays on Web Guides Consults & Submits to/Downloads from XML Registry Guides Participates in Guides Guides Evaluate,Use, Refine DOD Developer
Metadata Registry Working Group MRWG Objectives: • Review and implement DoD Metadata policy • Develop and promote best practices in metadata • Seek opportunities for convergence • Define Registry requirements, oversee development and operation • Determine what metrics to use, analyze and make recommendations to DoD and other policies • Participate, Respect, and Influence industry, international and coalition metadata (e.g., SQL, XML) standards Status: • 1999-05 – COE XML Registry IOC • 2000-10 – Namespace Mgrs Forum (NSMF) established (DISA COE CRCB) • 2005-06-08 – DoD Metadata Registry v5.0 beta status
DoD Metadata Registry • “One Stop” Publish & Subscribe for: • Build Time Structural Metadata Registration • Pulling Re-usable Data Components • Information Community Management • Current XML Gallery supporting 100,854 items (11 Nov 2005) • Now Supporting: • Database Structures • Reference Sets • XML Structures • Taxonomies • Transformations • More Products soon (e.g., ontologies, symbology) http://metadata.dod.mil
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 DoD Metadata Registry Users Discover and Pull metadata they are cleared for - Top Secret (SCI) Secret Unclassified (Sensitive) Unclassified (Open) Synchronized Components on Multiple Networks
DoD Metadata Registry Supports Mediation XSLT Legend • Convert XML to XML (and non-XML) • e.g., FIPS to ISO country codes, inches to centimeters • Report status (degree of success/failure) schema stylesheet sample 2004-ATO.xsd (schema) HasXSLT TransformsToXmlSchema notional 2005-2004-ATO.xsl (stylesheet) 2004-2005-ATO.xsl (stylesheet) TransformsToXmlSchema HasXSLT 2005-ATO.xsd (schema) XML Gallery Organizes Components for Mediation 2005-ATO.xml (sample) DescribedBy Registered in DoD Metadata Registry
Namespace Management TasksCoordination & Configuration Management • Coordinate Stakeholders • Establish and Run Coordination Venue(s) • Resolve Issues within Namespace • Coordination across Namespaces (bilateral, multilateral and/or via Metadata Registry Focus Group) • Oversee Development of structural metadata products • Submit Information Resource Packages to Metadata Registry • Vet Information Resources and Publish Status • Perform Versioning • Participate in Metadata Registry WG Leverage Existing Metadata Management
US491.2.W661864 DDMS - Catalog Card Template for the GIG DoD Discovery Metadata Specification (DDMS) Modern Warfare Modern Warfare Lee Grant Lee, R.E. Grant, U.S. • Coordination reflected in EO 13388 • DoD • IC • DHS • Justice Further Strengthening The Sharing Of Terrorism Information To Protect Americans Registered in Data Catalog(s) – NCES Content Discovery
DDMS FG • DDMS 1.0 • 2003-12 – DDMS FG established • Configuration Manage (CM) DDMS Specification • Develop and CM DDMS XML Schema (for use in HF & NCES pilots) • DDMS 1.1 • Simplification of DDMS 1.0 • Phase 1 response to Executive Order 13356 – “Sharing of Terrorism Information” – included in EO 13388 • Import of ICISM • DDMS 1.2 • Security Info on • Title, description, creator, publisher • DDMS 1.3 • Geospatial references using GML – Import of GML • Postal Address Example • Bounding Box Example • Bounding Geometry Example
Patterns for Visibility and Accessibility (content) xyz.xsd Structural Metadata Discovery DoD Metadata Registry ddms.xsd .xml .doc DDMS DDMS Payload Description Service Discovery Register Catalog Service Endpoint Service Registry .html DDMS .html DDMS sws.wsdl Catalog Introspection DDMS .jpg DDMS .gif Query Available Catalogs Unanticipated Consumer DDMS Data Catalog Web Service Data Catalog Enterprise Search DDMS DDMS DDMS DDMS Content Discovery DDMS DDMS SWS Query Catalog COI Enterprise
DDMS in NCES • Federated Search • Search Web Service (SWS) • DDMS-enabled Catalogs– implementing SWS • Enterprise Catalog – in pilot environment • Resource Metadata Harvesting Tools • DoD Metadata Registry • Taxonomy Gallery – inline DDMS record
Practical Utility for Taxonomies • Aid for organizing • Content • Services • Structural Metadata • Aid precision search via DDMS • Aid meaning resolution Country.sql ISO.xsd FIPS.xsd <ddms> : <Subject>…/MyCOI.owl#AlQaida</Subject> </ddms>
Taxonomies to Support Discovery DoD Core taxonomy Organization PoliticalOrganization UrCOI taxonomy MyCOI taxonomy Group TerroristOrganization sameAs ForeignTerroristOrganization TerroristGroup sameAs AlQaida al-Qaeda Producer View Consumer View <ddms> : <Subject>…/UrCOI.owl#TerroristGroup</Subject> </ddms> <ddms> : <Subject>…/MyCOI.owl#AlQaida</Subject> </ddms>
DoD Core Taxonomy v0.75c Product of Taxonomy Focus Group Encoded in OWL, then Registered in DoD Metadata Registry
Beyond Schema Validation • ebXML and the ICMWG expressing concern re: CM of enumerations • ICMWG support proposes enumerations not be included in the schema, but that an instance document identify its source/version for valid enumerations. • If some version of this approach is adopted, the run-time requirement will exist to query the enumeration source identified in the XML instance and any mediation that exists to retrieve the meaning for the valid value or to convert the code from one representation to the desired. These 2 XML chunks conform to the same schema, look different, but represent the same entity.
Taxonomy Gallery • Purpose • Provide visibility to manage and consume taxonomies • Enable COI oversight • Reuse • Harmonization • Support Discovery • Enable navigation within and among taxonomies • Even when producer and consumer do not share common taxonomy • Ensure availability • Persistent, immutable URL lowers risk of broken links • Technical Details • Implements W3C OWL (XML) as syntax for taxonomies • Each taxonomy is self-describing (registers via embedded DDMS) Includes DoD Core Taxonomy!
Taxonomy Tie-ins • Core Taxonomy Development • C2IEDM • METOC • DTIC • Registered Taxonomies • Focused Logistics • DHS • Work-in-Progress: Reference Sets • Feature Codes • FIPS Country Codes • Administrative Political Subdivision • Language Codes Inline DDMS record
TaxFG Status • 2004-01 – Taxonomy Focus Group formed, Objectives: • Core Taxonomy • Syntax for Core and COI taxonomies • Implementation of taxonomies via DDMS • 2004-05 – Taxonomy Gallery prototype • 2004-10 – Taxonomy Gallery IOC • 2005-02 – Finalized beta version of Core Taxonomy (v0.75c) • 2005-02 – White paper on stubbing • 2005-03 – Core (v0.75c) registered in Taxonomy Gallery
Core Enterprise Services (CES) Metadata FG Status • 2003-01 – CES Metadata WG formed • 2003-12 – DDMS XML Schema FG formed • 2004-01 – Taxonomy FG formed • 2005-02 • DDMS FG Status Briefed – DDMS 1.2 • Core Taxonomy FG Status Briefed – “Stubbing Exercise” • 2005-04 • DDMS FG Status Briefed – Change Requests • Core Taxonomy FG Status Briefed • New Initiative: “Design Guidelines for CES” • Naming conventions • Use of enumerations – Beyond Schema Validation
DDMS in SOAP Response - notional DDMS record
DDMS in Service Registration - notional DDMS record
DoD Guidance • DoD Dir 8320.2 Data Sharing in a Net-Centric Department of Defense 2004-12-02 • 4.2. Data assets shall be made visible by creating and associating metadata (“tagging”), including discovery metadata, for each asset. Discovery metadata shall conform to the Department of Defense Discovery Metadata Specification (reference (d)). http://www.dtic.mil/whs/directives/corres/html/83202.htm • Supporting Data Asset Visibility Guidance 2003-10-24 • A key DoD goal is to institutionalize the practice of advertising all data assets on the GIG by FY 2008. • By the FY 2006 program review, the Program Manager for any application, system and platform being developed, modified, or acquired will incorporate a requirement or capability description to create DDMS compliant discovery metadata for their data assets, and identify a date or release for implementation. The Program Manager will also incorporate a requirement or capability description to provide that metadata to a catalog and/or to generate an Enterprise search query response compliant with the defined discovery interface specification. http://www.defenselink.mil/nii/org/cio/doc/Data_Visibility_Component_Guidance_10-24-03signURL.pdf