Department of Homeland Security Metadata Center of Excellence

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 12/23/2021 11: 35 PM Office of the Chief Information Officer

Agenda u. Introduction u. The Big Picture: –Data Evolution –Information Sharing Use Case u. What is the DRM? –Description –Sharing –Context u. DRM Working Group u. Volume Strategy u. Revised DRM Structure u. Conclusion Office of the Chief Information Officer May 3, 2005 -- Pg. 2

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” Office of the Chief Information Officer May 3, 2005 -- Pg. 3

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

FEA Data Reference Model u Volume 1 is released. – http: //www. whitehouse. gov/omb /egov/a-1 -fea. html – Posted with comments on public wiki. u DRM Working Group is underway – Broad participation including State and Local – Foster broad adoption and implementation – Satisfy the Presidential Orders/Directives Office of the Chief Information Officer May 3, 2005 -- Pg. 5

DRM Use Case: Information Sharing Core Context COI Context Exchange 2 Discovery 3 Assembly packages Sharing Data Elems Description Org 1 Office of the Chief Information Officer Registry Data Elems 1 Components Org 2 May 3, 2005 -- Pg. 6

Information Sharing Use Case (1) u Markle Report. http: //www. markle. org/ – “Creating a Trusted Network for Homeland Security” u Vignette 3. – Scenario: Terrorists planning an attack on Rail lines using Chlorine gas Office of the Chief Information Officer May 3, 2005 -- Pg. 7

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

Information Sharing Use Case (3) u Agency Y needs data to perform analysis. u Agency Y discovers Agency X has the data it needs LOB Indicators Intel Infrastructure Protection Law Enforcement Facility Office of the Chief Information Officer Vulnerability Target Capability Lethal Agent Organization May 3, 2005 -- Pg. 9

Information Sharing Use Case (4) u Agency Y and Agency X assemble Exchange Packages. Incident Report + who + what + when + where + activity Police Incident Humint Report Threat Report Infrastructure Incident Critical Chemical Plant Office of the Chief Information Officer Target Capability Non-Critical Rail Yard Zoo May 3, 2005 -- Pg. 10

Information Sharing Use Case (5) u Data is exchanged. CIA Intel Threat Report Rail Yard Infrastructure Protection Law Enforcement Zoo Incident Chemical Plant Police Dept. Incident States Industry Analysis Center DHS DHS NCTC Law Analysis Center Shared Space Office of the Chief Information Officer May 3, 2005 -- Pg. 11

Information Sharing Use Case (6) u Data is associated in a shared space. Shared Space Threat Report 1 Capability: Chlorine Gas Incident 1: Zoo Office of the Chief Information Officer Incident 2: Police Target: Rail Lines Incident 3: Chemical Incident 4: Rail Yard May 3, 2005 -- Pg. 12

What is the DRM? (1) - Describe Answers: How do we make our data interoperable? u Logical Data Modeling. – Class, Property, Data Type, Association u Goals: – Unambiguous, Defined, Registered u Logical Data Model != RIM Office of the Chief Information Officer May 3, 2005 -- Pg. 13

What is the DRM? (2) - Discover Answers: How does a class of users find relevant information? u Taxonomy – Article at XML. com “Formal Taxonomies for the Federal Government” u Context is more than categorization. – Data Asset Directory (Data Source Context? ) – Business Rules Office of the Chief Information Officer May 3, 2005 -- Pg. 14

Formal Taxonomies u Formal Node Definition – Collection, Class, Instance u Formal Link Definition – part. Of, subclass. Of, instance. Of Car Engine Transmission Car Wheel Carburetor Sports Car Corvette SUV Sedan Mustang ** From 4/15/05 presentation at Library of Congress Office of the Chief Information Officer May 3, 2005 -- Pg. 15

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

DRM Working Group u. Three tiers – Public participation • Virtual via “Wiki” • Quarterly F 2 F Forums – Team participation • 5 Teams. 1 Lead, 2 Editors, Contributors • Bi-Weekly Meetings – Executive Committee • Dispute Resolution • Weekly Meetings Exec Teams Public u. DRM Project Coordinator – cheryl. manns@associates. dhs. gov Office of the Chief Information Officer May 3, 2005 -- Pg. 17

Volume Strategy u. 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 u. Rotating Team Meetings – Team Leader and editor meeting. – General Team meeting. – Separate Volume Team Meetings u. Next Steps – Volume Outlines with each section Defined – Milestone Schedule Office of the Chief Information Officer May 3, 2005 -- Pg. 18

Revised DRM Structure – V 0. 2** Context Subject Area Subject Class Association Who What Sharing When Service Context Service Class Input/Output Association Information Access Exchange Class Exchange Payload Association Structured Semi-Structured Unstructured Data Asset Class Association Where Why Information Exchange Description Data Asset Directory Unique Identifiers Query Class Association Entity Description Entity Class Entity Property Association Resource Description S E C U R I T Y P R I V A C Y Resource Class Association ** Requires distinction between metamodel and model Office of the Chief Information Officer May 3, 2005 -- Pg. 19

DRM Schema (Draft Overview) (1 of 5) NOTE: ONLY ILLUSTRATIVE! <Data. Reference. Model> <Data. Description> <Data> </Data> <Data. Assets></Data. Assets> </Data. Description> <Data. Sharing> <Exchanges> </Exchanges> <Data. Access> </Data. Sharing> <Data. Context> <Taxonomies> </Taxonomies> <Fea. Map> </Fea. Map> <Data. Standards> </Data. Context> </Data. Reference. Model> Office of the Chief Information Officer May 3, 2005 -- Pg. 20

DRM Schema (Description) (2 of 5) <Data> NOTE: ONLY ILLUSTRATIVE! <Structured. Data> <Entity rdf: id=""> <Entity. Name></Entity. Name> <Attributes> <Attribute name="" datatype="" /> </Attributes> <Relationships> … </Relationships> </Entity> </Structured. Data> <Unstructured. Data> <Resource rdf: id="resource 01"> <dc: title>CIRCULAR NO. A-130</dc: title> <dc: format>HTML</dc: format> <dc: creator>OMB</dc: creator> <dc: Identifier>url</dc: Identifier> </Resource> </Unstructured. Data> </Data> Office of the Chief Information Officer May 3, 2005 -- Pg. 21

DRM Schema (Description) (3 of 5) NOTE: ONLY ILLUSTRATIVE! <Data. Description> </Data> <!– continued … --> <Semi. Structured. Data> <Entity /> <Resource /> </Semi. Structured. Data> </Data> <Data. Assets> <Data. Asset> <Owning. Agency /> <Steward /> <Registered href="" /> <Type> </Type> <Point. Of. Contact> </Data. Asset> </Data. Assets> </Data. Description> Office of the Chief Information Officer May 3, 2005 -- Pg. 22

DRM Schema (Sharing) (4 of 5) <Exchanges> NOTE: ONLY ILLUSTRATIVE! <Exchange. Package> <Sender /> <Recipient /> <Classification /> <Entity. Ref idref="" /> <Category. Ref idref="" /> <!-- other attributes. . . --> </Exchange. Package> </Exchanges> <Data. Access> <Query. Point> <Query. Language> </Query. Language> <Endpoint /> <Result. Format /> <Entities. Ref> <Entity. Ref /> </Entities. Ref> <Access. Control /> <Data. Asset. Ref /> </Query. Point> </Data. Access> Office of the Chief Information Officer May 3, 2005 -- Pg. 23

DRM Schema (Context) (5 of 5) NOTE: ONLY ILLUSTRATIVE! <Taxonomies> <Taxonomy rdf: id="federal_irm"> <Node rdf: id="node 14"> <Node. Name> … </Node. Name> <Definition>. . . </Definition> <Node. Children> <Node rdf: id="node 15"> </Node. Children> </Node> </Taxonomy> </Taxonomies> <Fea. Map> <Link type="SRM" from="node 11" to="114514"> </Link> </Fea. Map> <Data. Standards> <Standard rdf: id="" href=""> </Standard> </Data. Standards> Office of the Chief Information Officer May 3, 2005 -- Pg. 24

Conclusion u How you can help! – http: //colab. cim 3. net/cgibin/wiki. pl? Data. Reference. Model – 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 Office of the Chief Information Officer May 3, 2005 -- Pg. 25

Questions? Office of the Chief Information Officer May 3, 2005 -- Pg. 26