1 / 26

Department of Homeland Security Metadata Center of Excellence

Learn about the Data Reference Model (DRM) evolution, elements, and prescription in the context of Homeland Security. Michael C. Daconta, a metadata expert, shares insights on metadata exchange, sharing, and registry. Explore the DRM structure revisions, working groups, and the importance of data in today's digital age. Discover how the DRM facilitates information sharing and exchange in various scenarios, from agency collaboration to crisis response. Dive into formal taxonomies, data modeling, and interoperability concepts essential for secure data sharing and access in the Homeland Security domain.

irenechang
Download Presentation

Department of Homeland Security Metadata Center of Excellence

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. Department of Homeland Security Metadata Center of Excellence The Evolution of the Data Reference Model:Elements of Prescription and Description Michael C. Daconta Metadata Program Manager May 17, 2005

  2. Agenda • Introduction • The Big Picture: • Data Evolution • Information Sharing Use Case • What is the DRM? • Description • Sharing • Context • DRM Working Group • Volume Strategy • Revised DRM Structure • Conclusion

  3. Personal Introduction • Michael C. Daconta • Author/co-author of 10 Technical books • C, C++, Java, XML, Semantic Web • Experience: • Lead for the DOD/IC Core Taxonomy • Chief Architect for DOD’s Net-Centric Enterprise Services Collateral Space & DIA’s Virtual Knowledge Base • Inventor of the Fannie Mae Electronic Mortgage Standard (2 patents) • Recent Article on XML.com • “Formal Taxonomies for the Federal Government”

  4. Data Evolution Timeline GIGO/minis/micros www / Netscape Web services OWL Age of Proprietary Data Age of Semantic Models Age of Programs Age of Open Data Age of Open Metadata Program-Data Text, Office Docs Databases (proprietary schema) HTML, XML (open schema) Namespaces, Taxonomies, RDF Ontologies & Inference 1945 -1970 1970 - 1994 1994 - 2000 2000 - 2003 2003 - Procedural Programming Object-Oriented Programming Model-Driven Programming “Data is less important than code” “Data is as important as code” “Data is more important than code” ** From my article in Enterprise Architect Magazine

  5. FEA Data Reference Model • Volume 1 is released. • http://www.whitehouse.gov/omb/egov/a-1-fea.html • Posted with comments on public wiki. • DRM Working Group is underway • Broad participation including State and Local • Foster broad adoption and implementation • Satisfy the Presidential Orders/Directives

  6. Core Context COI Context Context Discovery Exchange Assembly Sharing packages Components Description Data Elems Data Elems Org 2 Org 1 Registry DRM Use Case: Information Sharing 2 3 1

  7. Information Sharing Use Case (1) • Markle Report. http://www.markle.org/ • “Creating a Trusted Network for Homeland Security” • Vignette 3. • Scenario: Terrorists planning an attack on Rail lines using Chlorine gas

  8. Terrorist Organization + name Rail Yard Zoo Incident + when + where + what + who Chemical Plant Terrorist Organization: + name: “Al Qaeda” Terrorist Chemical + name Chemical + name: “Chlorine” Person Information Sharing Use Case (2) • Agency X collects data. • Using the DRM, Agency X creates metadata that describes this data in an unambiguous manner.

  9. Information Sharing Use Case (3) • Agency Y needs data to perform analysis. • Agency Y discovers Agency X has the data it needs LOB Indicators InfrastructureProtection Intel Vulnerability Capability Law Enforcement Lethal Agent Target Facility Organization

  10. Information Sharing Use Case (4) • Agency Y and Agency X assemble Exchange Packages. Incident Report + who + what + when + where + activity Humint Report Threat Report Police Incident Infrastructure Incident Target Capability Critical Non-Critical Chemical Plant Rail Yard Zoo

  11. Intel Threat Report CIA States Industry Analysis Center Incident Rail Yard DHS InfrastructureProtection Incident Zoo DHS Incident Law Enforcement Chemical Plant DHS NCTC Law Analysis Center Incident Police Dept. Shared Space Information Sharing Use Case (5) • Data is exchanged.

  12. Information Sharing Use Case (6) • Data is associated in a shared space. Shared Space Threat Report 1 Target: Rail Lines Capability: Chlorine Gas Incident 1: Zoo Incident 2: Police Incident 3: Chemical Incident 4: Rail Yard

  13. What is the DRM? (1) - Describe Answers: How do we make our data interoperable? • Logical Data Modeling. • Class, Property, Data Type, Association • Goals: • Unambiguous, Defined, Registered • Logical Data Model != RIM

  14. What is the DRM? (2) - Discover Answers: How does a class of users find relevant information? • Taxonomy • Article at XML.com “Formal Taxonomies for the Federal Government” • Context is more than categorization. • Data Asset Directory (Data Source Context?) • Business Rules

  15. Car Car Engine Wheel Sports Car SUV Sedan Transmission Carburetor Corvette Mustang Formal Taxonomies • Formal Node Definition • Collection, Class, Instance • Formal Link Definition • partOf, subclassOf, instanceOf ** From 4/15/05 presentation at Library of Congress

  16. What is the DRM? (3) - Share Answers: How do we effectively exchange and access information? • National Information Exchange Model (NIEM) • Developing “Core” Interagency XML Exchanges • Currently: DHS, DOJ, DOT, NIST • Not Part of DRM Working Group • http://www.NIEM.gov

  17. Exec Teams Public DRM Working Group • Three tiers • Public participation • Virtual via “Wiki” • Quarterly F2F Forums • Team participation • 5 Teams. 1Lead, 2 Editors, Contributors • Bi-Weekly Meetings • Executive Committee • Dispute Resolution • Weekly Meetings • DRM Project Coordinator • cheryl.manns@associates.dhs.gov

  18. Volume Strategy • Change the volume strategy from the current plan by creating cohesive volumes around functional lines. • Volume 1. Overview LEAD: Michael Daconta, DHS • Volume 2. DRM Management Strategy LEAD: Suzanne Acar, DOI • Volume 3. Data Description LEAD: Larry Fitzwater, EPA • Volume 4. Data Sharing LEAD: Bryan Aucoin, IC CIO • Volume 5. Data Context LEAD: James Feagans, DOJ • Sections in each of the above volumes on Security & Privacy • Rotating Team Meetings • Team Leader and editor meeting. • General Team meeting. • Separate Volume Team Meetings • Next Steps • Volume Outlines with each section Defined • Milestone Schedule

  19. Context Data Asset Directory Service Context Subject Context Subject Area Service Class SEC U RITY Subject Class Data Asset Class PRI V AC Y Input/Output Association Association Association Who When What Why Where Sharing Information Exchange Information Access Exchange Class Unique Identifiers Exchange Payload Query Class Association Association Description Entity Description Resource Description Structured Entity Class Semi-Structured Resource Class Entity Property Unstructured Association Association ** Requires distinction between metamodel and model Revised DRM Structure – V0.2**

  20. DRM Schema (Draft Overview) (1 of 5) <DataReferenceModel> <DataDescription> <Data> </Data> <DataAssets></DataAssets> </DataDescription> <DataSharing> <Exchanges> </Exchanges> <DataAccess> </DataAccess> </DataSharing> <DataContext> <Taxonomies> </Taxonomies> <FeaMap> </FeaMap> <DataStandards> </DataStandards> </DataContext> </DataReferenceModel> NOTE: ONLY ILLUSTRATIVE!

  21. DRM Schema (Description) (2 of 5) <Data> <StructuredData> <Entity rdf:id=""> <EntityName></EntityName> <Attributes> <Attribute name="" datatype="" /> </Attributes> <Relationships> … </Relationships> </Entity> </StructuredData> <UnstructuredData> <Resource rdf:id="resource01"> <dc:title>CIRCULAR NO. A-130</dc:title> <dc:format>HTML</dc:format> <dc:creator>OMB</dc:creator> <dc:Identifier>url</dc:Identifier> </Resource> </UnstructuredData> </Data> NOTE: ONLY ILLUSTRATIVE!

  22. DRM Schema (Description) (3 of 5) NOTE: ONLY ILLUSTRATIVE! <DataDescription> </Data> <!– continued … --> <SemiStructuredData> <Entity /> <Resource /> </SemiStructuredData> </Data> <DataAssets> <DataAsset> <OwningAgency /> <Steward /> <Registered href="" /> <Type> </Type> <PointOfContact> </PointOfContact> </DataAsset> </DataAssets> </DataDescription>

  23. DRM Schema (Sharing) (4 of 5) <Exchanges> <ExchangePackage> <Sender /> <Recipient /> <Classification /> <EntityRef idref="" /> <CategoryRef idref="" /> <!-- other attributes ... --> </ExchangePackage> </Exchanges> <DataAccess> <QueryPoint> <QueryLanguage> </QueryLanguage> <Endpoint /> <ResultFormat /> <EntitiesRef> <EntityRef /> </EntitiesRef> <AccessControl /> <DataAssetRef /> </QueryPoint> </DataAccess> NOTE: ONLY ILLUSTRATIVE!

  24. DRM Schema (Context) (5 of 5) NOTE: ONLY ILLUSTRATIVE! <Taxonomies> <Taxonomy rdf:id="federal_irm"> <Node rdf:id="node14"> <NodeName> … </NodeName> <Definition>...</Definition> <NodeChildren> <Node rdf:id="node15"> </Node> </NodeChildren> </Node> </Taxonomy> </Taxonomies> <FeaMap> <Link type="SRM" from="node11" to="114514"> </Link> </FeaMap> <DataStandards> <Standard rdf:id="" href=""> </Standard> </DataStandards>

  25. Conclusion • How you can help! • http://colab.cim3.net/cgi-bin/wiki.pl?DataReferenceModel • Join a Volume Team! • Government sponsor can email: susan.turnbull@gsa.gov • Contribute to a Volume • Subscribe to DRM-public mailing list • Participate in the Public Forum • Date: June 13 • Location: Mitre

  26. Questions?

More Related