EPA Region 3 XML Web Services Pilot Project

1
EPA Region 3 XML Web Services Pilot Project

• The Team Debra Forman, John Graves, Brand
  Niemann (technical consultant), and Brian Trulear
• June 14, 2002

2
Overview

• 1. Background
• 2. Information Design and Architecture
• 3. Proposed Work Statement
• 4. Demonstration of Stage 1 Prototype
• 5. Some Next Steps

3
1. Background

• 1.1 February 27 - 28 Region 3/Mid-Atlantic
  States Information Management Meeting,
  Philadelphia, PA.
• XML Web Services Training and Presentation of
  Region 3 and Chesapeake Bay Program Pilot-Part 1.
• Region 3 Pilot Team Formed.
• 1.2 March 13 - 14 OEI National Meeting, Chicago,
  IL.
• XML Web Services Training and Discussion of
  Region 5 Pilot Projects (Interagency wetlands
  data integration).
• 1.3 April 11 Chesapeake Bay Program Information
  Management Subcommittee, Annapolis, MD.
• Presentation of Region 3 and Chesapeake Bay
  Program Pilot-Part 2.
• PASDA (Pennsylvania Spatial Data Access) Interest
  in Participating.
• 1.4 June 10-13 EPA-State TRG/Node 1.0 Meeting,
  Philadelphia, PA.
• Region 3 Discussion of Work Statement and
  Demonstration of the Stage 1 Prototype.

4
2. Information Design and Architecture

• Requirements
• Use XML content network technology to integrate
  the content over the Region 3 network and the
  Internet and to update it.
• Start with a subset of the content to build a
  working prototype (Stage 2-see Slide 9) within 60
  days and then add more content to it to make it
  an EPA portal to be demonstrated at the Second
  OEI National Meeting in November 2002.

5
2. Information Design and Architecture
Distributed Content Sources
WordPerfect Document
Web Pages Database
LOTUS 123 Spreadsheet
Access XP Database
Note Use Manage Content to update if not
accessible
Software Platform
NXT 3
123
WordPerfect
DEFAULT
Access
Folders
XML
html
.WK3
.MDB
DTD
XML
XML
XSD
html
XSL
6
2. Information Design and Architecture

• Menu
• Watershed Restoration
• Sensitive Populations
• Enhancing Responsible Development
• Explanation
• Short descriptions of each menu item with an
  icon.
• A template will be provided for each content
  source with a link between it and the data
  sources.
• The templates were developed by a business
  process and need to be implemented to automate
  that recurrent business process (yearly or so).

7
2. Information Design and Architecture
8
3. Proposed Work Statement

• 1. EPA Region 3 will provide a server running
  Windows NT Service Pack 6a connected to the
  internet and LAN (s) that meet the minimum
  requirements for running NXT3 3.3 and reach the
  required content.
• 2. NextPage will install the NXT3 software and
  EPA Region 3 will identify the location (URLs,
  mapped drives, etc) for the content to be
  integrated and provide samples for prototyping.
• 3. EPA Region 3 will provide directions for the
  hierarchical system of folders and interface for
  accessing the distributed content to NextPage
  along with the work flow specification for
  updating each piece of content.
• 4. NextPage will install the working prototype on
  the Region 3 server and demonstrate the
  capabilities, especially, the implementation of
  the workflow for the updating of content from
  distributed locations (nodes) and instantaneous
  refresh of reports.
• 5. EPA Region 3 will provide a list of
  refinements to the working prototype to NextPage.
• 6. NextPage will deliver the refinement to the
  working prototype for Region 3.

9
4. Demonstration of Stage 1 Prototype

• Prototype in three stages
• Stage 1 Manual aggregation and repurposing of
  content using the NextPage LivePublish at one
  non-EPA location can demonstrate live updating.
• Stage 2 Network aggregation of content and
  repurposing using the NextPage NXT 3 at one EPA
  server location.
• Stage 3. Network integration of content using the
  NextPage NXT 3 at multiple EPA server locations
  where necessary.

10
4. Demonstration of Stage 1 Prototype
11
4. Demonstration of Stage 1 Prototypehttp//130.1
1.44.240/lpBin22/lpext.dll?ftemplatesfnmain-j.h
tm2.0
12
4. Demonstration of Stage 1 Prototypehttp//130.1
1.44.240/lpBin22/lpext.dll?ftemplatesfnmain-j.h
tm2.0
13
5. Some Next Steps

• 5.1 Clarify the work flow process.
• 5.2. Refine the Work Statement and decide on the
  60 day schedule.
• 5.3 Demonstrate Stage 1 Prototype to John
  Armstead and present the Work Statement.
• 5.4 Process the Subcontract for NextPage.
• 5.5 Prepare the EPA Region 3 Server for NextPage
  to work on.
• 5.6 Track the EPA Geospatial Metadata and Data
  Network Pilots in Region 3 and 5 (see next slide).

14
5. Some Next Steps EPA Geospatial Metadata and
Data Network

• Use of GML (XML for geospatial data) is our CIOs
  priority and is described in the Geospatial
  Blueprint A Strategic Plan for the EPA
  Geospatial Program (May 2002 draft).
• The Regions and Program Offices have begun to
  pilot the use of XML for geospatial metadata and
  the use of GML/OWS (Open Web Services) for the
  integration of diverse and distributed geospatial
  data.
• Vendors are starting to release new products that
  include the OpenGIS Consortiums specifications
  for geospatial interoperability (e.g. Ionic
  Enterprise-see next slide).
• A pilot XML/GML content network for integrating
  distributed geospatial metadata and data is in
  process for EPA Region 3 (see next slide).

15
5. Some Next Steps EPA Geospatial Metadata and
Data Network
Web Browser
Mobile/Wireless Devices
IONIC Portrayal Engine (GML-to-SVG, etc.)
IONIC Web Services Framework (Proprietary-to-GML
Converters)
LandView/ Cameo CD/DVDs
State of PA PASDA
USGS
EPA Region 3 and CBP
EPA WME