1 / 26

Brand Niemann EPA Data Architect and CIOC Best Practices Committee SICoP Co-Chair January 30, 2007

A Segment Architecture for Cross-Agency Semantic Interoperability of Water Resources Using DRM 3.0 and Web 3.0. Brand Niemann EPA Data Architect and CIOC Best Practices Committee SICoP Co-Chair January 30, 2007. Contents. 1. Abstract 2. History 3. Semantics in Enterprise Architecture

kioko
Download Presentation

Brand Niemann EPA Data Architect and CIOC Best Practices Committee SICoP Co-Chair January 30, 2007

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. A Segment Architecture for Cross-Agency Semantic Interoperability of Water Resources Using DRM 3.0 and Web 3.0 Brand Niemann EPA Data Architect and CIOC Best Practices Committee SICoP Co-Chair January 30, 2007

  2. Contents • 1. Abstract • 2. History • 3. Semantics in Enterprise Architecture • 4. Segment Architecture for Water Resources • 5. Recommendations

  3. Abstract • Significant milestone events in bringing semantic interoperability, technology, and the Web to the Agency that shows “A little semantic goes a long way.”* (Section 2). • The role of semantics in enterprise architecture and especially the new segment architecture (Section 3). • A segment architecture to achieve cross-agency semantic interoperability of water resources data and information (Section 4). • Recommendations tied to the overall OEI Action Plan and for the individual offices (OIC, OTOP, and OIAA) (Section 5). * Professor Jim Hendler, in SICoP White Paper Series Module 1: Introducing Semantic Technologies and the Vision of the Semantic Web to the Federal CIO Council, February 16, 2005.

  4. 2. History • 1. Mark Forman-Quad Council 2002 FOSE CIO Showcase of Excellence Special Award for Innovation, March 20, 2002. Leads to the CIOC’s Web Services WG and SICoP. • 2. First Semantic Technology for E-Government Conference, White House Conference Center, September 8, 2003, EPA CIO (Kim Nelson) Keynotes and EPA Business Case (Bill Sonntag) Featured! (see SICoP White Paper Module 1 and 4th Semantic Interoperability for E-Government Conference, February 8-9, 2006) • 3. Semantic Interoperability Study Interest Group (SISIG) Begins for the CIOC AIC Leadership (Kim Nelson, Co-Chair), December 8, 2004. • 4. Demonstrations of Semantic Technology Pilot Projects for Senior EPA Managers, August 16, 2004 (Brenda Smith, EPA GIO).

  5. 2. History • 5. DRM Information Sharing Tool Kit and Applications: Part 1 Involving EPA Region 4 at the Collaborative Expedition Workshop, Designing the DRM for Data Visibility, July 18, 2005 (Part of Major Semantic Technology for EPA Region 4 Program). • 6. Implementing the Semantic Web Part 1. Semantic Technology Profile for the Data Reference Model: Use Case 2: U.S. EPA Digital Harbor Pilot Presentation, August 22, 2005. • 7. EPA Data Architecture for DRM 2.0 CoP Begins, February 22, 2006. • 8. Building DRM 3.0 and Web 3.0 for the EPA CIO and CIOC Best Practices Committee, January 18, 2007.

  6. 2. History • November 29, 2006, EPA/OTOP Business Intelligence and Analytics (BIA) User Group (UG) Meeting: • BIA UG, Business Objects, and Informatica. • Greatly assisted in this interactive session by Phil Magrogan (LMCO), who along with Steve Hufford, received the Special Recognition for Best Breakout Session Presentation at our recent 2nd SOA for E-Government Conference as judged by the IAC SOA Committee.

  7. 2. History • 1. Educate and empower the three user groups using common tools (BIA, SAS, and Statistics) to produce and register their applications as standard web services, otherwise they are not really useable/reusable in an agency SOA. We can and will pilot this to provide examples. • 2. Maintain competition among the tools vendors to support open standards for metadata so the tools produce interoperable metadata, not proprietary metadata (e.g. Business Objects demonstrated their new product LiveOffice that takes Microsoft Office proprietary formats and puts them into another proprietary format!) I have already spoken with senior management at Business Objects about this because they want to participate in one of our SICoP pilots on semantic interoperability of person data and we told them what they need to do to be interoperable with the other vendors in the pilot. • 3. Add semantic interoperability to what Informatica does for us. SICoP already has several pilots that demonstrate this.

  8. 3. Semantics in Enterprise Architecture Source: June 2, 2006, EPA Data Architecture for DRM 2.0 Fact Sheet with Slide 63, The Evolution of the EA Solutions Space by TopQuadrant Inc., “Role of Ontology Architecture in an Integrated Lifecycle Approach”, Semantic Technology Conference 2006, Fairmont Hotel, San Jose, CA, March 6-9, 2006. Also published in the Journal of Enterprise Architecture, August 2005, pp. 45-52.

  9. 3. Semantics in Enterprise Architecture • Building DRM 3.0 and Web 3.0 for Managing Context Across Multiple Documents and Organizations: • 3a. Brief Explanation of the Title • 3.b The FEA Data Reference Model 2.0 • 3.c DRM 2.0 Implementation Metamodel • 3.d SICoP Knowledge Reference Model • 3.e Concept Map of DRM 2.0 • See February 6, 2007, SICoP Special Conference: • http://colab.cim3.net/cgi-bin/wiki.pl?SICoPSpecialConference_2007_02_06

  10. 3a. Brief Explanation of the Title • A. DRM 3.0 – Suggest change to DRM 2.0 to Unify Description and Context. • IKRIS Program and New ISO Standard for Common Logic. • B. Web 3.0 – Model Documents on the Web. • Topics (unstructured data), Fields (semi-structured data) and Data Elements (structured data) can be give precise definitions within an overall context that can be reasoned over (e.g. WordNet ontology). • C. Managing Context Across Multiple Documents and Organizations – Use Semantic Wikis for Collaboration. • Best Practice Examples: SICoP, CIA and NCOIC

  11. 3.b The FEA Data Reference Model 2.0 DRM 1.0 SICoP All Three unify DRM 3.0 Ontologies Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pp. 2-3. http://www.whitehouse.gov/omb/budintegration/expanding_egov_2005.pdf

  12. 3.c DRM 2.0 Implementation Metamodel Note: The Data Network makes these links visible and searchable! • Definitions: • Metamodel: Precise definitions of constructs and rules needed for abstraction, generalization, and semantic models. • Model: Relationships between the data and its metadata - W3C. • Metadata: Data about the data for: Discovery, Integration, and Execution. • Data: Structured e.g. Table, Semi-Structured e.g. Email, and Unstructured e.g. Paragraph. Source: Professor Andreas Tolk, 2005, and DRM 2.0 Implementation Through Iteration and Testing Report, October 15, 2005.

  13. 3.d SICoP Knowledge Reference Model Ontology The point of this graph is that Increasing Metadata (from glossaries to ontologies) is highly correlated with Increasing Search Capability (from discovery to reasoning).

  14. 3.e Concept Map of DRM 2.0 Is_a Recall Slide 3 and see next slide for explanation.

  15. 3.e Concept Map of DRM 2.0 • Essentially a Data Model of a Data Model! • PDF Version for Use in a Document, SVG Version for Use on the Web, XML Version for Structure, OWL Version for Semantic Relationships, and Simple Text Version. • Source: Brand Niemann, Jr., Informal Communication, October 28, 2006, as part of the October 11, 2006, Birds of a Feather Meeting on National Information Sharing Standards at the Fifth Semantic Interoperability for E-Government Conference, October 10-11, 2006. • http://colab.cim3.net/file/work/SICoP/2006-10-10/NatilStandards_10_11_2006.doc • See Concept Maps Home Page at http://cmap.ihmc.us/

  16. 4. Segment Architecture for Water Resources Source: FEA Practice Guidance, “Value to the Mission”, December 2006, Federal Enterprise Architecture Program, Management Office, OMB, 45 pp.

  17. 4. Segment Architecture for Water Resources • Make the relationships between: • 1. enterprise architecture • A management practice for transitioning from the current state to the desired future state. • 2. segment architecture, and • Detailed results-oriented architecture (baseline and target) and transition strategy for common, shared, or enterprise services. • 3. solution architecture • An architecture for an individual IT system that is part of a segment. • real using SOA in White Papers, Workshops/Conferences, and Pilots. See Collaborative Expedition Workshop #57, Tuesday, January 23, 2007 at NSF , Opening Up Networked Improvement Activities Around Service Oriented Architecture in 2007

  18. 4. Segment Architecture for Water Resources P: Primary Purpose S: Secondary Purpose/Benefit * Suggested by Bill Sonntag, January 18, 2007.

  19. 4. Segment Architecture for Water Resources • Definitions of Acronyms for Phases: • GES: EPA’s Guide to Selected National Environmental Statistics in the U.S. Government (1995). • See http://web-services.gov • OW: EPA Office of Water Data Element Harmonization Project (1998). • See http://web-services.gov • SWRR: CEQ’s Sustainable Water Resources Roundtable (2004). • See http://acwi.gov/swrr. • CA: Composite Applications (Business Ontology Platform) (2006). • See Digital Harbor Pilots for DRM 2.0 Implementation Work at SICoP 4th Semantic Interoperability for E-Government Conference, February 8-9, 2006, and for EPA OW (Mark Hamilton). • Implementing the Semantic Web Part 1. Semantic Technology Profile for the Data Reference Model: Use Case 2 - U.S. EPA, August 24, 2005, as part of EPA Data Architecture for DRM 2.0, August 7, 2006, Briefing. Also see press coverage at http://www.gcn.com/print/25_9/40462-1.html

  20. 4. Segment Architecture for Water Resources • Definitions of Terms for Functionalities: • Metadata: Data about the data for Discovery, Integration, and Execution where Data is Structured (e.g. Table), Semi-Structured (e.g. Email), and Unstructured (e.g. Paragraph) (DRM 2.0). • Harmonization: To understand and deal with the common problem of say ‘are “Lead” and “Pb” the same, nearly the same, or different?’ as used by different people in different contexts. • Enhanced Search: Search across all three types of Data (see Metadata definition above). • Mashups: A website or application that combines content from more than one source into an integrated experience (repurposing) • Source: Wikipedia at http://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)

  21. 4. Segment Architecture for Water Resources • Metadata Elements: • Department or Agency • Office • Program Title • Summary Program Description • Data Coverage • Collection Methods • Collection Frequency • Geographic Coverage • Contacts (Public Inquires) • Publications • Databases Note: The original DOS version and the Windows 98 version did not support structured tables and Web graphics formats.

  22. 4. Segment Architecture for Water Resources Note: One of three reports with data element harmonization tables and appendices on this project.

  23. 4. Segment Architecture for Water Resources Note: Expanded format for each Indicator plus links to actual data!

  24. 4. Segment Architecture for Water Resources See Executable Integration of the FEA Reference Models in Composite Applications Fact Sheet at http://web-services.gov/SICoPPilotFactSheet_Final.pdf

  25. 5. Recommendations • OIC Action Plan: • Establish and implement additional data standards to improve data quality and promote opportunities for data integration and analysis. • See http://web-services.gov for EPA and the CIOC Best Practice Committee’s SICoP • OIAA Action Plan: • Present, understand, and improve what EPA knows about the current state of the environment through development and maintenance of an Indicators decision support portal. • See http://www.sdi.gov for EPA and the Council on Environmental Quality.

  26. 5. Recommendations • OTOP Action Plan: • Converged Network of Services and Expand EPA Portal capabilities to facilitate open collaboration with internal and external partners (Include Semantic Desktop and Semantic Wikis) • See http://colab.cim3.net/cgi-bin/wiki.pl?BrandNiemann • Data Architect (Train When Arrives): • See http://colab.cim3.net/cgi-bin/wiki.pl?EPADataArchitectureforDRM2 • OEI Action Plan: • Digitization of Library Holdings to Allow Greater Search Capability and Access: • Google Library Partnerships Team Offer • Environmental Information Symposium: • Semantic Technology and Semantic Web Expert for Closing Panel (Did and Continue with Pilots) • Work across EPA (and the government-my words) to foster linkages between environmental indicators (and performance indicators-my words) and Agency strategic planning, including data acquisition. • My current for “making a little semantic go a long way!”

More Related