Region 4 Semantic Technologies Pilot

1
Region 4 Semantic Technologies Pilot

• Briefing to the EPA Office of Environmental
  Information Board of Directors, March 2, 2005
• Brand Niemann, EA Team, Office of Technology
  Operations and Planning
• Co-Chair, Semantic Interoperability Community of
  Practice (SICoP)

2
Overview

• The Semantic Interoperability Community of
  Practice (SICoP) Grew Out of the First Semantic
  Technologies for E-Government Conference, White
  House Conference Center, September 8, 2003.
• SICoP Was Chartered by the Knowledge Management
  Working Group of the CIO Councils Best Practices
  Committee in March 2004.
• SICoP is Producing Three Best Practices
  Modules
• (1) Introducing Semantic Technologies and the
  Vision of the Semantic Web (completed)
• (2) The Business Case for Semantic Technologies
  (in process for April 8, 2005 and September 2005)
• (3) Implementing the Semantic Web (in process for
  September 2005)

3
Overview

• SICoP is Conducting Pilot Projects at the Request
  of the FEA
• Formal Taxonomies ( Ontologies) for the U.S.
  Government (see next slide)
• Federal Enterprise Reference Model Ontology (FEA
  RMO)
• Semantic Technology Profiles for the FEA Data
  Reference Model
• The National Infrastructure for Community
  Statistics (NICS) CoP is using the Region 4
  Pilot as a Business Use Case.
• SICoP is Producing Workshops and Conferences
• Second Semantic Technologies for E-Government
  Conference, September 8-9, 2004
• XML 2004 Conference, November 14-17, 2004
  (Keynote Session Tracks)
• Semantic Interoperability Study Group for the
  Architecture Infrastructure Committee
  Leadership, October-December 2004
• Monthly Collaboration Expedition Workshops with
  the Architecture Infrastructure Committee at
  NSF (e.g. December 9, 2004, and February 22,
  2005)
• Semantic Web Applications for National Security
  Conference Jointly with the DARPA/DAML Program,
  April 7-8, 2005 (see slide 5)
• The Third Semantic Technologies for E-Government
  Conference, September 2005

4
Formal Taxonomies for the U.S. Government

• OWL Listing
• lt?xml version"1.0"?gt ltrdfRDF xmlnsrdf"http//w
  ww.w3.org/1999/02/22-rdf-syntax-ns"
  xmlnsxsd"http//www.w3.org/2001/XMLSchema"
  xmlnsrdfs"http//www.w3.org/2000/01/rdf-schema"
  xmlnsowl"http//www.w3.org/2002/07/owl"
  xmlnsdaml"http//www.daml.org/2001/03/damloil"
  xmlns"http//www.owl-ontologies.com/unnamed.owl
  " xmlnsdc"http//purl.org/dc/elements/1.1/"
  xmlbase"http//www.owl-ontologies.com/unnamed.ow
  l"gt ltowlOntology rdfabout""/gt ltowlClass
  rdfID"Transportation"/gt ltowlClass
  rdfID"AirVehicle"gt ltrdfssubClassOf
  rdfresource"Transportation"/gt lt/owlClassgt
  ltowlClass rdfabout"GroundVehicle"gt
  ltrdfssubClassOf rdfresource"Transportation"/gt
  lt/owlClassgt ltowlClass rdfabout"Automobile"gt
  ltrdfssubClassOfgt ltowlClass rdfID"GroundVehicle
  "/gt lt/rdfssubClassOfgt Etc.

Transportation Class Hierarchy
Source Formal Taxonomies for the U.S.
Government, Michael Daconta, Metadata Program
Manager, US Department of Homeland Security,
XML.Com, http//www.xml.com/pub/a/2005/01/26/formt
ax.html
5
Semantic Web Applications for National Security
Conference
Keynotes Demos Early Adopters Tutorials Pilot
Advice Trade Show Etc.
https//www.schafertmd.com/swans/
6
Background

• February 23 and March 2, 2005, Adding Value While
  Having Fun With EPA Data!
• February 16, 2005, Federated Repository Pilot
  Update for EPA.
• February 10, 2005, Semantic Interoperability
  Community of Practice Enablement (SCOPE) for the
  EPA Region 4 Pilot.
• November 22, 2004, Toward an EPA Data Reference
  Model.
• November 10, 2004, The FEA Data and Information
  Reference Model (DRM) Information Sharing.
• November 1, 2004, Federal Region 4 Semantic
  Interoperability Pilot Project Community of
  Practice and Plans.
• October 19, 2004, Building Enterprise
  Architecture through Web Services for Remote
  Portlets (WSRP) in Sample EPA Regional Portal.

7
Paradigm Shift
Target Architecture
CoP
Goals
Business
Ontology
Breakthrough Performance Communities of Practice
(BP CoPs) Doing Value-Driven Enterprise
Architecture Using Distributed Semantic Web
Services
Data
Applications
Technology
Baseline Architecture

• Pilot Examples
• GeoResponse.Com
• Logidex Asset Center
• Region 4 Pilot
• Phase One Workplace
• Portal (Oracle 10g-WSRP)
• Phase Two Semantic
• Interoperability Network
• (Knowledge Management)

High Performance Organizations (HPO) Doing Complia
nce-Based Enterprise Architecture Using Centralize
d Services
8
GeoResponse - Voice GIS Multimodal
Notification

• Features
• Report an Event
• Geocode the Event
• Define the Call List
• Customize your Message
• Make the Call
• Track and Map Responses
• Trigger another Process
• Award-winning VoiceXML Web Service from
  Broadstrokes at GeoResponse.com to be featured at
  the SWANS Conference Trade Show, April 7-8, 2005.
• Recently integrated with WSRP/CAP in cooperation
  with Starbourne/Oracle Team.
• Similar to DHS/DOJ Information Sharing Use Case
  (February 28, 2005)!

Implementing the Norfolk Southern Graniteville
Derailment Scenario for the new Emergency
Response Architecture!
9
Federated Repository Pilot
Increasing levels of support for the strategic
management of ITIM initiatives automating all
levels of SDA usage, real-time metrics collection
FEA-CapableEnterprise SDA Repositories
EnterpriseTechnologies

• Accurate in real- time
• Strategic Management
• FEA Maturity
• Strategic Process Changes
• Savings

Niche Applications
LogicLibrary
Logidex Flashline.com, Inc.
Personal Productivity Tools
Popkin SA Metis
Niche Repositories (XML, .PPT,
FEAMS, A300db, CollabNet,
ComponentSource) SCM (ClearCase,
SourceSafe, PVCS)
StarOffice Excel, Word
PowerPoint
Individuals / Workgroups No re-use inventory Does
not support classification activities Manual
versioning Laborious manual data collection,
cleansing, verification, and reporting
Workgroups Multiple, un-coordinated re-use
inventories Multiple schemes for
classification Supports at least one asset type
asset types vary by product Version control Some
have addl functionality, like collaboration
Unique to Logidex Enhanced federation
capabilities Launch from Portals, or w/in IDEs,
or collaboration s/w like Groove v3.0 Automated
discovery of reusable assets S/W for component
certification QA Open API for use of Semantic
Search s/w like Vivisimo
Division / Department Manual/ modeled/ static
inventories support for asset types
varies Coordinated scheme for classification Some
associative / linkage capabilities Supports
multiple asset types Supports governance and
version control
Agency / Cross Agency (as desired) supports all
ITIM business processes Automated metrics
collection re tangible asset inventories (not
static models provides real-time/ actual info
for what if modeling in Metis and Popkin) FEA
CPIC-specific linkage / associative abilities
FEA, Agency EA(s), Reference Models, TOGAF,
DODAF, Exhibit 300s, etc. Link to multiple
repositories for single source of information
about an asset Support ALL asset types,
lifecycles, governance requirements,
versioning Coordinated scheme for classification
10
Gartner Magic Quadrant 2004
Challengers
Leaders
DHS MCOE Vendor Proof of Concept for
Metadata Repository Selection By April 1st (see
next slide)

Allen Sys


Ability
LogicLibrary

to
Flashline



Execute
Adaptive
Fujitsu

MetaMatrix

DAG

CS

Troux
Unicorn
Ascential



CA/ModelManager
Select

Note For 2005 CA is removed from the Leader
Quadrant.
Informatica
Sybase
As of 2/04
Through 2005
Niche Players
Visionaries
Completeness of Vision
11
DHS MCOE Vendor Proof of Concept for Metadata
Repository Selection

• Industry Proof of Concept Scenarios
• Day 1 Installation, Configuration, Security
• Day 2 Load Assets and Discovery
• Day 3 Data Harmonization, Discovery, and Web
  Services
• Day 4 Federated Query, Security, Vendor
  Architecture and Wrap-up
• Vendors
• MetaMatrix (Previous Pilot)
• Rochade/Allen Systems Group
• SoftwareAG (Previous Pilot)
• Imagis Technologies
• Unicorn (Logic Library) (Previous Pilot)

12
The Recommended Business Case for the Target
Architecture

• Evolve EPA EA to "Solutions Architecture"
  supported by a Federated Repository so the EA
  Team, Program Offices, and Contractors have a
  tool to manage not only all the EA artifacts but
  also the actual software component development
  and reuse assets.
• Evolve the Portal Project with Central Services
  to decomposing the Central Services into
  re-useable distributed Web Service components to
  be managed and promoted to the agency, EPA
  partners, and the rest of the government.

13
OASIS Web Services for Remote Portlets
OASIS Web Services for Remote Portals Web Site
http//oasis-open.org/committees/wsrp
14
Federal Region 4 Semantic Interoperability Pilot
Project
Oracle 10g Demonstration Shows WSRP
Producer-Consumer-User Roles
Demonstration Available on Secure Internal Oracle
Server by Invitation
15
Current Ontology for Region 4 Pilot
16
Current Ontology-Driven Information System for
Region 4 Pilot
Integration of EPA Content and Interoperability
with Non-EPA Content!
17
Current Ontology-Driven Information System for
Indicators
Note the folder names are either the ontology or
the knowledgebase instances.
18
Current Ontology-Driven Information System for
FHA/NHIN
Examples
SUMO
HL7 RIM FEA-RMO
EON SNOMED CT LOINC
Source Netcentric Semantic Linking (Mapping) An
Approach for Enterprise Semantic
Interoperability, Mary Pulvermacher, et. Al.
MITRE, October 2004.
19
Current Ontology-Driven Information System for
Region 4 Pilot

• The structure and semantics the comes from
  modeling Web content, documents, and databases,
  gives us
• What was said in press,
• What the science says,
• What the data says, and
• What infrastructure and planning we need to
  support all this.
• Imagine Semantic Web Services that give us a
  preview of the search results before we do the
  search to help us do a better search!
• Imagine Semantic Web Services that help us
  harmonize the semantics across the enterprise!
• Can you say machine-processable, integrated, and
  interoperable data and metadata!

20
Some Next Steps for the Region 4 Pilot

• The Ontology-driven Information System is the
  Target Architecture!
• Use the CoP-Wiki-SUMO to build more ontology
  definitions, hierarchy, instances, and
  associations.
• This provides the evolving structure and gaps to
  fill clearly shows what we have and what we
  need.
• Region 4 and its partners have excellent content!
  (see example to right)
• Suggested Upper Merged Ontology (see
  http//www.ontologyportal.org