XML Web Services: Enterprise Architecture Brand Niemann (from XML Web Services Evangelist to Solutions Architect) Office o...
Overview <ul><li>1. Enterprise Architecture </li></ul><ul><li>2. E-Government Initiatives </li></ul><ul><li>3. EPA Enterpr...
1. Enterprise Architecture <ul><li>Enterprise architecture – a description, in useful models, diagrams, and narrative, of ...
<ul><li>Enterprise Architecture (continued) </li></ul><ul><li>Enterprise architecture – both for the current environment a...
2. E-Government Initiatives <ul><li>The E-Government Task Force found that the federal government could significantly impr...
2. E-Government Initiatives <ul><li>In addition, the e-Authentication initiative and the Enterprise E-Government Architect...
2. E-Government Initiatives <ul><li>Portfolios: </li></ul><ul><ul><li>Government to Citizen (G2C) (5): </li></ul></ul><ul>...
2. E-Government Initiatives <ul><li>So far government agencies have avoided the kind of extensive re-engineering that e-go...
3. EPA Enterprise Architecture <ul><li>Dedicated staff: Chief Architect and eight Team Members. </li></ul><ul><li>EPA’s ar...
4. XML Web Services <ul><li>Why XML?: </li></ul><ul><ul><li>The eXtensible Markup Language became a World Wide Web Consort...
4. XML Web Services <ul><li>What is XML?: </li></ul><ul><ul><li>XML is a standard for preserving and communicating informa...
4. XML Web Services
4. XML Web Services   The Web Services Standards “stack” <ul><li>Commonly used by the major vendors: </li></ul><ul><ul><li...
4. XML Web Services <ul><li>XML.Gov, June 19, 2002: </li></ul><ul><ul><li>E-Gov Solutions Architects Working Group (SAWG),...
4. XML Web Services <ul><li>Software Development Lifecycle Models: </li></ul><ul><ul><li>Classical Software Development: <...
4. XML Web Services
4. XML Web Services <ul><li>Document Framework Design – Advanced XML Application Development: </li></ul><ul><ul><li>Schema...
4. XML Web Services <ul><li>Document Framework Design – Advanced XML Application Development (continued): </li></ul><ul><u...
4. XML Web Services
4. XML Web Services
5. Architecture of An EPA XML Web Service <ul><li>Enter your zip code to retrieve environmental information about your com...
5. Architecture of An EPA XML Web Service
5. Architecture of An EPA XML Web Service   http://www.epa.gov/ceppo/lepclist.htm
5. Architecture of An EPA XML Web Service   http://130.11.53.73/lepc/FMPro?-db=LEPC.FP5&-format=-fmp_xml&zip_lepc::zip_cod...
5. Architecture of An EPA XML Web Service   http://130.11.53.73/brand.vxml
5. Architecture of An EPA XML Web Service   http://studio.tellme.com/
5. Architecture of An EPA XML Web Service   1-866-745-7735 <ul><li>Welcome to the E. P. A. Local Emergency Planning Commit...
6. Architecture of XML Web Services Pilots Projects <ul><li>6.1 EPA Geospatial Data Index (FileMaker): </li></ul><ul><ul><...
6. Architecture of XML Web Services Pilots Projects <ul><li>Evolution*: </li></ul><ul><ul><li>6.1 XML using HTTP GET and P...
6.1 EPA Geospatial Data Index (FileMaker)
6.1 EPA Geospatial Data Index (FileMaker)
6.2 EPA-Census Population Estimation
Filemaker with Population database End User with web browser Web server HTML w/javascript lat/long/ radius request xml req...
6.3 EPA-State Content Network National Environmental Information Exchange Network
6.3 EPA-State Content Network
6.3 EPA-State Content Network NXT 3 Platform Architecture and Services (SCOTS*) *Standards-based Commercial Off-the-Shelf ...
6.3 EPA-State Content Network Build Your Own Enterprise Architecture!
6.3 EPA-State Content Network Submit and Manage Distributed Content
6.3 EPA-State Content Network A Content Node for Every EPA Office, Program, Region, State, and Partner
6.3 EPA-State Content Network Integrating Environmental Content Networks <ul><li>Earth 911: </li></ul><ul><ul><li>Started ...
6.4 EPA Region 3 and EPA Region 5 NXT 3 WordPerfect Document Web Pages Database LOTUS 123 Spreadsheet Access XP Database W...
6.4 EPA Region 3 and EPA Region 5 LandView/ Cameo CD/DVDs State of PA PASDA USGS EPA Region 3 CBP EPA WME IONIC Web Servic...
6.4 EPA Region 3 and EPA Region 5 <ul><li>Notes on schematic diagram: </li></ul><ul><ul><li>GML makes it possible to rende...
6.4 EPA Region 3 and EPA Region 5
6.5 E-Gov (E-records)
6.5 E-Gov (Business Compliance)
6.5 E-Gov (Geospatial Information)
7. Some Next Steps <ul><li>Work together on incorporating XML Web Services in the EPA EA work. </li></ul><ul><ul><li>Educa...
7. Some Next Steps   XML Separates Content from Presentation Content Presentation Traditional Content Network: Integrated ...
7. Some Next Steps   XML Meta Data Matrix Resource Perspective Client Perspective External Embedded Centralized Distribute...
7. Some Next Steps XML Meta Data Architecture <ul><li>XML data and meta data architectures are connected. </li></ul><ul><l...
7. Some Next Steps XML Meta Data Architecture <ul><li>Client-server approaches to meta data work when there are a small nu...
7. Some Next Steps “Hierarchical Peer-to-Peer” Diagram Key: Client Nodes (outer circles); Server Nodes (inner circles)
7. Some Next Steps “Hierarchical Peer-to-Peer” Diagram <ul><li>Centralized meta data sources pass queries from server to s...
7. Some Next Steps   “True Peer-to-Peer” Diagram Key: Peer Nodes (all circles)
7. Some Next Steps   “True Peer-to-Peer” Diagram <ul><li>Makes each networked client a server of the meta data that it has...
7. Some Next Steps “PIE:” Presence, Identity, and Edge Resources Resources at the  Center  migrate to the  Edge , anonymou...
7. Some Next Steps “PIE:” Presence, Identity, and Edge Resources <ul><li>The third generation of the Internet. </li></ul><...
8. Contact Information <ul><li>Brand Niemann, Ph.D. </li></ul><ul><ul><li>USEPA Headquarters, EPA West, Room 6143D </li></...
Upcoming SlideShare
Loading in …5
×

XML Web Services: Enterprise Architecture

3,126 views

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,126
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

XML Web Services: Enterprise Architecture

  1. 1. XML Web Services: Enterprise Architecture Brand Niemann (from XML Web Services Evangelist to Solutions Architect) Office of Environmental Information US EPA June 26, 2002
  2. 2. Overview <ul><li>1. Enterprise Architecture </li></ul><ul><li>2. E-Government Initiatives </li></ul><ul><li>3. EPA Enterprise Architecture </li></ul><ul><li>4. XML Web Services </li></ul><ul><li>5. Architecture of An EPA XML Web Service </li></ul><ul><li>6. Architecture of XML Web Services Pilots Projects </li></ul><ul><li>7. Some Next Steps </li></ul><ul><li>8. Contact Information </li></ul>
  3. 3. 1. Enterprise Architecture <ul><li>Enterprise architecture – a description, in useful models, diagrams, and narrative, of the mode of operation for an enterprise (agency): </li></ul><ul><ul><li>Logical terms – interrelated business processes and business rules, information needs and flows, and work locations and users. </li></ul></ul><ul><ul><li>Technical terms – hardware, software, data, communications, and security attributes and standards. </li></ul></ul>
  4. 4. <ul><li>Enterprise Architecture (continued) </li></ul><ul><li>Enterprise architecture – both for the current environment and for the target environment, as well as the transition plan for sequencing from the current to the target environment. </li></ul><ul><li>Enterprise architecture – clarify and help optimize the dependencies and relationships among the agency’s business operations and the underlying IT infrastructure and applications that support these operations. </li></ul><ul><li>Source: GAO Report on Challenges in Managing and Preserving Electronic Records, June 2002, page 28. </li></ul>
  5. 5. 2. E-Government Initiatives <ul><li>The E-Government Task Force found that the federal government could significantly improve customer service over the next 18 to 24 months by focusing on 24 high-payoff, government-wide initiatives that integrate agency operations and IT investments. These initiatives could generate several billion dollars in savings by reducing operating inefficiencies, redundant spending and excessive paperwork. The initiatives will provide service to citizens in minutes or hours, compared to today’s standard of days or weeks. Moreover, by leveraging IT spending across federal agencies, the initiatives will make available over $1 billion in savings from aligning redundant investments. </li></ul>
  6. 6. 2. E-Government Initiatives <ul><li>In addition, the e-Authentication initiative and the Enterprise E-Government Architecture Project were added to address key barriers. The E-Government Architecture project will carry out two major concurrent activities: </li></ul><ul><ul><li>One of the activities will be the development of a architecture, toward the development of a Federal Enterprise Architecture, for each of the current E-Government initiatives, as well as a core set of standardized technology models to facilitate technology solutions. </li></ul></ul><ul><ul><li>The second activity will be the collection and analysis of business and data architecture information across the federal government to identify new opportunities for E-Government initiatives and elimination of redundancy. Initially this effort will focus on four key areas including Homeland Security, economic stimulus, social services, and back office operations. </li></ul></ul><ul><li>Source: E-Government Strategy, February 27, 2002. </li></ul>
  7. 7. 2. E-Government Initiatives <ul><li>Portfolios: </li></ul><ul><ul><li>Government to Citizen (G2C) (5): </li></ul></ul><ul><ul><ul><li>E.g., Recreation One-Stop </li></ul></ul></ul><ul><ul><li>Government to Business (G2B) (5): </li></ul></ul><ul><ul><ul><li>E.g., Business Compliance One-Stop </li></ul></ul></ul><ul><ul><li>Government to Government (G2G) (5): </li></ul></ul><ul><ul><ul><li>E.g., Geospatial Information One-Stop </li></ul></ul></ul><ul><ul><li>Internal Effectiveness and Efficiency (IEE) (8): </li></ul></ul><ul><ul><ul><li>E.g., E-Records Management </li></ul></ul></ul><ul><li>Cross-cutting: </li></ul><ul><ul><li>e-Authentication </li></ul></ul><ul><li>Infrastructure: </li></ul><ul><ul><li>Federal Enterprise Architecture </li></ul></ul><ul><li>Source: http://egov.gov/egovreport-3.htm </li></ul>
  8. 8. 2. E-Government Initiatives <ul><li>So far government agencies have avoided the kind of extensive re-engineering that e-government will require to be truly effective. Instead Federal agencies have been busy re-creating the stovepipes in cyberspace. </li></ul><ul><li>Agencies are likely to exhibit significant resistance to dismantling niche business units and processes, fearing that doing so will result in loss control, funding and ultimately mission. </li></ul><ul><li>As e-government matures, its focus will shift from simply providing online access to pre-existing services to offering new services and new ways of doing things. </li></ul><ul><li>The newness will beg for a kind of methodology that allows success to be defined when e-government projects begin to cross agency jurisdictions or involve public/private collaboration. </li></ul><ul><li>Source: Measuring e-gov, Federal Computer Week, April 8, 2002, pp 20-21. </li></ul>
  9. 9. 3. EPA Enterprise Architecture <ul><li>Dedicated staff: Chief Architect and eight Team Members. </li></ul><ul><li>EPA’s architecture effort was rated a stage 3 out of 5 in a recent GAO report, placing EPA in the top 20% of all federal agencies who reported. </li></ul><ul><li>Completion of a draft baseline architecture assessment for the Environmental Information Architecture business domain. </li></ul><ul><li>Incorporated a large number of modeling and analysis tools in the baseline applications inventory. </li></ul><ul><li>Suggested that it include XML Web Services. </li></ul><ul><li>Source: EPA Enterprise Architecture, Quarter 2, Fiscal Year 2002(Jan-Mar 2002). </li></ul>
  10. 10. 4. XML Web Services <ul><li>Why XML?: </li></ul><ul><ul><li>The eXtensible Markup Language became a World Wide Web Consortium (W3C) standard in 1998 as the universal format for structured documents and data on the Web (http://www.w3.org/XML/). </li></ul></ul><ul><ul><li>The CIO Council created the XML Working Group in 2000 to facilitate the efficient and effective use of XML through cooperative efforts among government agencies, including partnerships with commercial and industrial organizations (http://xml.gov/). </li></ul></ul><ul><ul><li>GAO report to Congress urges government to adopt XML and that Federal Agencies address XML in their enterprise architectures (http://www.gao.gov/new.items/d02327.pdf). </li></ul></ul><ul><ul><li>XML Web Services is what OMB’s Mark Forman is encouraging in the E-Gov Initiatives and especially for the “collect once, use many” knowledge management projects like the Geospatial Information One-Stop (http://egov.gov). </li></ul></ul>
  11. 11. 4. XML Web Services <ul><li>What is XML?: </li></ul><ul><ul><li>XML is a standard for preserving and communicating information – encoding, tagging, and internationalizing – that will be everywhere. </li></ul></ul><ul><ul><li>Web Services provide communication between applications running on different Web servers that will bring the Internet to its new level. </li></ul></ul><ul><ul><li>XML Web Services are applications running on different devices that communicate XML data using XML messages. </li></ul></ul><ul><ul><li>XML Web Services for geospatial data use the OpenGIS Consortium’s GML (Geography Markup Language) and OWS (Open Web Services) standards and specifications. </li></ul></ul><ul><ul><li>Web Services can and should be interoperable across multiple vendor tools and platforms in the enterprise (see http://www.ws-i.org/Community.aspx). </li></ul></ul>
  12. 12. 4. XML Web Services
  13. 13. 4. XML Web Services The Web Services Standards “stack” <ul><li>Commonly used by the major vendors: </li></ul><ul><ul><li>Work Flow (WFDL-Work Flow Description Language). </li></ul></ul><ul><ul><li>Publication and Discovery (UDDI-Universal Description, Discovery, and Integration). </li></ul></ul><ul><ul><li>Service Description (WSDL-Web Services Description Language). </li></ul></ul><ul><ul><li>Messaging (XMLP-XML Protocol from SOAP-Simple Object Access Protocol). </li></ul></ul><ul><ul><li>Content (XML-Extensible Markup Language). </li></ul></ul><ul><ul><li>Transport (HTTP-Hypertext Transport Protocol). </li></ul></ul>
  14. 14. 4. XML Web Services <ul><li>XML.Gov, June 19, 2002: </li></ul><ul><ul><li>E-Gov Solutions Architects Working Group (SAWG), Federal Enterprise Architecture – Program Management Office: </li></ul></ul><ul><ul><ul><li>The usage of XML, Web Services, UDDI, SOAP, etc. (Lead-Marion Royal, Co-Chair XML Working Group) </li></ul></ul></ul><ul><ul><ul><li>Leveraging emerging technologies and industry-proven standards (J2EE, MS.NET, XML, XML Web Services) </li></ul></ul></ul><ul><ul><ul><li>Assignment of a Solution Architect to each of the 24 e-Gov initiatives. </li></ul></ul></ul><ul><ul><li>XML Registry/Repository – Business Case Analysis: </li></ul></ul><ul><ul><ul><li>Booz Allen Hamilton complete the A-11 Exhibit 300 </li></ul></ul></ul><ul><ul><ul><li>Registries describing and pointing to business services (i.e., web services) offer higher value than registries that provide only XML definitions and classifications (i.e., XML Schemas). </li></ul></ul></ul><ul><ul><li>XML Web Services Working Group Proposed: </li></ul></ul><ul><ul><ul><li>Natural role for Government as a provider of raw data in standard format (XML) to private sector, who add value. </li></ul></ul></ul>
  15. 15. 4. XML Web Services <ul><li>Software Development Lifecycle Models: </li></ul><ul><ul><li>Classical Software Development: </li></ul></ul><ul><ul><ul><li>Typically begins with a high-level architecting process which includes modeling the software objects and their interactions. Next an editor is used to write the source code using procedural programming languages (C/C++, Java, etc.) according to proper syntax and the compiler is invoked to translate and link the software to an executable binary format. Finally, a debugger is used to catch any errors, thereby ensuring correct program behavior. </li></ul></ul></ul><ul><ul><li>Modern XML Software Development: </li></ul></ul><ul><ul><ul><li>XML technologies are significantly different from classical procedural programming languages both in structure, syntax and nature. XML application development is also a completely different process that begins with the development of the content model using XML Schema or DTDs (see schematic diagram in next slide). </li></ul></ul></ul><ul><li>Source: XML Spy Integrated Development Environments, White Paper, 18 pp., 2002 (http://www.xmlspy.com) </li></ul>
  16. 16. 4. XML Web Services
  17. 17. 4. XML Web Services <ul><li>Document Framework Design – Advanced XML Application Development: </li></ul><ul><ul><li>Schema Modeling: An iterative process which involves initial requirements analysis, use-cases, as well as examination of existing data schemas. Additional refinements are required to map all of the elements of your XML Schema to the underlying database (relational or XML-based) or content management system. </li></ul></ul><ul><ul><li>Data Flow and Process Modeling: The flow of information gathered by a document framework must be modeled from content author (non-technical domain experts), transported to the database, and then to content consumers (typically customers, partners, etc.). </li></ul></ul>
  18. 18. 4. XML Web Services <ul><li>Document Framework Design – Advanced XML Application Development (continued): </li></ul><ul><ul><li>Transformation Modeling: XSLT has a two-fold critical role in both the input templates that are used by content creators and the output stylesheets that are required by the content consumers and must be designed to fit the data flow and process model determined earlier. </li></ul></ul><ul><ul><li>Implementation: The business logic and user interface of a document framework application must be custom developed, but can be easily implemented using any of the leading Internet application development platforms (e.g., J2EE, Microsoft .NET web Services, Oracle Application Server, etc.) </li></ul></ul>
  19. 19. 4. XML Web Services
  20. 20. 4. XML Web Services
  21. 21. 5. Architecture of An EPA XML Web Service <ul><li>Enter your zip code to retrieve environmental information about your community: </li></ul><ul><ul><li>Local Emergency Planning Committee (LEPCs) provide a forum for emergency management agencies, responders, industry and the public to work together to understand chemical hazards in the community, develop emergency plans in case of an accidental release, and always look for ways to prevent chemical accidents. Local industries must provide information to LEPCs about chemical hazards, LEPCs are required by law to make this information available to any citizen who requests it. You can make a difference by attending an LEPC meeting or joining your LEPC. </li></ul></ul><ul><ul><ul><li>Please Note: Currently we have over 3000 listings in our LEPC Database. It is our goal to provide the most current and accurate information. We look to the LEPC community to help us successfully meet this goal. Please forward any changes or corrections to Dana Robinson. These changes will be incorporated and updated monthly. </li></ul></ul></ul>
  22. 22. 5. Architecture of An EPA XML Web Service
  23. 23. 5. Architecture of An EPA XML Web Service http://www.epa.gov/ceppo/lepclist.htm
  24. 24. 5. Architecture of An EPA XML Web Service http://130.11.53.73/lepc/FMPro?-db=LEPC.FP5&-format=-fmp_xml&zip_lepc::zip_code=22181&-find=
  25. 25. 5. Architecture of An EPA XML Web Service http://130.11.53.73/brand.vxml
  26. 26. 5. Architecture of An EPA XML Web Service http://studio.tellme.com/
  27. 27. 5. Architecture of An EPA XML Web Service 1-866-745-7735 <ul><li>Welcome to the E. P. A. Local Emergency Planning Committee finder. </li></ul><ul><li>Please speak or touch-tone your 5 digit Zipcode. </li></ul><ul><li>84040 </li></ul><ul><li>Here are results for the Zipcode 84040. </li></ul><ul><li>The L. E. P. C. nearest to you is listed in the E. P. A. database as follows. Davis County. At Davis County Sheriffs Department located in the city of Farmington. </li></ul><ul><li>Thank You for calling, goodbye. </li></ul>
  28. 28. 6. Architecture of XML Web Services Pilots Projects <ul><li>6.1 EPA Geospatial Data Index (FileMaker): </li></ul><ul><ul><li>Region 1 and 10 want to submit updates as XML Web Services. </li></ul></ul><ul><li>6.2 EPA-Census Population Estimation: </li></ul><ul><ul><li>Part of LandView 5 (XML Web Service using Vultus (desktop applications to XML Web Services portlets) in process. </li></ul></ul><ul><li>6.3 EPA-State Content Network: </li></ul><ul><ul><li>Multiple applications and public/private partnership with Earth 911 (MS.NET) to integrate environmental content networks. </li></ul></ul><ul><li>6.4 EPA Region 3 (current OEI Lead Region) and EPA Region 5 (future OEI Lead Region): </li></ul><ul><ul><li>GML/OWS tasks in Geospatial Blueprint Report (May 22, 2002). </li></ul></ul><ul><li>6.5 E-Gov: </li></ul><ul><ul><li>E-records, Business Compliance, and Geospatial Information </li></ul></ul>
  29. 29. 6. Architecture of XML Web Services Pilots Projects <ul><li>Evolution*: </li></ul><ul><ul><li>6.1 XML using HTTP GET and POST. </li></ul></ul><ul><ul><li>6.2 XML and Java. </li></ul></ul><ul><ul><li>6.3 XML, SOAP/XMLP (XML messaging), XML metadata (RDF), and XML content adapters in a e-content network platform. </li></ul></ul><ul><ul><li>6.4 All the previous plus GML/OWS (Open Web Services). </li></ul></ul><ul><ul><li>6.5 All the previous plus Enterprise Content Networking and XForms. </li></ul></ul><ul><li>* From individual services to chaining together of services. </li></ul>
  30. 30. 6.1 EPA Geospatial Data Index (FileMaker)
  31. 31. 6.1 EPA Geospatial Data Index (FileMaker)
  32. 32. 6.2 EPA-Census Population Estimation
  33. 33. Filemaker with Population database End User with web browser Web server HTML w/javascript lat/long/ radius request xml request xml file 1 2 3 4 5 <ul><li>End user enters URL for HTML page </li></ul><ul><li>End user enters latitude/longitude and radius, presses “Get Population” button </li></ul><ul><li>Javascript in web page issues URL to Filemaker for the census block records </li></ul><ul><li>Filemaker sends XML file back to the web page </li></ul><ul><li>Javascript reads the XML file, performs calculations, updates the web page. </li></ul>
  34. 34. 6.3 EPA-State Content Network National Environmental Information Exchange Network
  35. 35. 6.3 EPA-State Content Network
  36. 36. 6.3 EPA-State Content Network NXT 3 Platform Architecture and Services (SCOTS*) *Standards-based Commercial Off-the-Shelf Software
  37. 37. 6.3 EPA-State Content Network Build Your Own Enterprise Architecture!
  38. 38. 6.3 EPA-State Content Network Submit and Manage Distributed Content
  39. 39. 6.3 EPA-State Content Network A Content Node for Every EPA Office, Program, Region, State, and Partner
  40. 40. 6.3 EPA-State Content Network Integrating Environmental Content Networks <ul><li>Earth 911: </li></ul><ul><ul><li>Started in Arizona in 1991. </li></ul></ul><ul><ul><li>Recognized by EPA and others in 1995 with a Presidential Environmental Technology Initiative grant to expand nationwide dubbing it “Earth’s 911”. </li></ul></ul><ul><ul><li>Recipient of the Stockholm Challenge Award for Information Technology in September 2001 (742 nominations from 90 countries). Referred to as the Nobel Prize for the IT society. </li></ul></ul><ul><ul><li>Recently called “the future of e-government” by allowing thousands to upload their community information through a password protected user interface and be made available to the public in real time (Web and 800 phone number). </li></ul></ul><ul><ul><li>Earth 911 model replicated to Pets 911 with the goal of ending the needless euthanasia of over 5 million healthy adoptable pets in the United States. </li></ul></ul><ul><ul><li>Uses state-of-the-art hardware and software technology (AT&T, Hewlett-Packard, and Microsoft) including Visual Studio.Net for XML Web Services with information organized by ZIP code and state. </li></ul></ul><ul><ul><li>The Earth 911 Foundation is a 501 (c) 3 non-profit organization with a staff of about 40 support by grants and contributions. </li></ul></ul>
  41. 41. 6.4 EPA Region 3 and EPA Region 5 NXT 3 WordPerfect Document Web Pages Database LOTUS 123 Spreadsheet Access XP Database WordPerfect XML DTD DEFAULT html html 123 .WK3 XML Access .MDB XML XSD XSL Folders Distributed Content Sources Software Platform Note: Use Manage Content to update if not accessible
  42. 42. 6.4 EPA Region 3 and EPA Region 5 LandView/ Cameo CD/DVDs State of PA PASDA USGS EPA Region 3 CBP EPA WME IONIC Web Services Framework (Proprietary-to-GML Converters) IONIC Portrayal Engine (GML-to-SVG, etc.) Web Browser Mobile/Wireless Devices
  43. 43. 6.4 EPA Region 3 and EPA Region 5 <ul><li>Notes on schematic diagram: </li></ul><ul><ul><li>GML makes it possible to render legacy and third-party data and services interoperable – minimizing the coupling between components – by “wrapping” existing systems. </li></ul></ul><ul><ul><li>The forthcoming GML 3.0 will include support for SML (Sensor Modeling Language) for real-time spatial data network data streams. </li></ul></ul><ul><ul><li>Geospatial objects can be created, updated, and/or deleted through the Web Browser and Mobile/Wireless Devices. </li></ul></ul><ul><ul><li>LandView/Cameo would also use CD/DVD encryption and the CITRIX Terminal Web Server for secure access needs (e.g., Homeland Security and EPA Situation Room). </li></ul></ul>
  44. 44. 6.4 EPA Region 3 and EPA Region 5
  45. 45. 6.5 E-Gov (E-records)
  46. 46. 6.5 E-Gov (Business Compliance)
  47. 47. 6.5 E-Gov (Geospatial Information)
  48. 48. 7. Some Next Steps <ul><li>Work together on incorporating XML Web Services in the EPA EA work. </li></ul><ul><ul><li>Education and outreach. </li></ul></ul><ul><ul><li>Pilot projects. </li></ul></ul><ul><ul><li>Use the new paradigms (see next slides). </li></ul></ul><ul><li>Collaborate on the presentation to the CIO Architecture Work Group in September. </li></ul><ul><li>Coordinate presentations on the EA and XML Web Services Pilot Projects at the Second OEI National Meeting (November). </li></ul>
  49. 49. 7. Some Next Steps XML Separates Content from Presentation Content Presentation Traditional Content Network: Integrated Portal Content Network: “ Uber” Portal Personalization: Customer Relationship Management Centralized Distributed Centralized Distributed
  50. 50. 7. Some Next Steps XML Meta Data Matrix Resource Perspective Client Perspective External Embedded Centralized Distributed HTML <META> RDDL http://www.rddl.org RSS http://www.purl.org/rss/1.0/ Annotea http://www.w3.org/2001/Annotea/ UDDI http://www.uddi.org Open Directory Project http://dmoz.org Outside case of little interest.
  51. 51. 7. Some Next Steps XML Meta Data Architecture <ul><li>XML data and meta data architectures are connected. </li></ul><ul><li>From a Resource Perspective, meta data is either external to or embedded within the data. </li></ul><ul><li>From a Client Perspective, meta data is either centralized or distributed . </li></ul><ul><li>There are standards efforts in each of the three areas of the 4 by 4 matrix. The combination of Centralized –Embedded meta data is of little interest. </li></ul>
  52. 52. 7. Some Next Steps XML Meta Data Architecture <ul><li>Client-server approaches to meta data work when there are a small number of known sources of meta data. </li></ul><ul><li>Peer-to-peer approaches are needed in an more distributed environment to simultaneously query, discover, and aggregate the results locally. </li></ul><ul><li>The architecture of peer-to-peer systems is instructive in the design of meta data applications using distributed external meta data. </li></ul>
  53. 53. 7. Some Next Steps “Hierarchical Peer-to-Peer” Diagram Key: Client Nodes (outer circles); Server Nodes (inner circles)
  54. 54. 7. Some Next Steps “Hierarchical Peer-to-Peer” Diagram <ul><li>Centralized meta data sources pass queries from server to server on behalf of a particular client. </li></ul><ul><li>Combines the convenience for the client of needing to contact and communicate with only one server with the convenience of distributing the task of meta data aggregation across a number of servers. </li></ul><ul><li>Any given client node must know the address of the server node which forms its point of contact for the network. </li></ul>
  55. 55. 7. Some Next Steps “True Peer-to-Peer” Diagram Key: Peer Nodes (all circles)
  56. 56. 7. Some Next Steps “True Peer-to-Peer” Diagram <ul><li>Makes each networked client a server of the meta data that it has aggregated from its local machine. </li></ul><ul><li>There is no distinction between nodes which generate queries and nodes which provide answers – any node may be a source of both queries and results sets - queries will eventually travel to all parts of the network to seek its results set. </li></ul><ul><li>This form of distributed meta data architecture is expected to become more prevalent. </li></ul>
  57. 57. 7. Some Next Steps “PIE:” Presence, Identity, and Edge Resources Resources at the Center migrate to the Edge , anonymous users gain Identity , and transient connectivity yields to Presence . Ability to detect whether that resource is accessible in real time. Presence P Name for one of the resources -- a machine, a document, or a person. Identity I Content, storage cycles, bandwidth and even human attention. Edge Resources ER Explanation Name PIE Pieces
  58. 58. 7. Some Next Steps “PIE:” Presence, Identity, and Edge Resources <ul><li>The third generation of the Internet. </li></ul><ul><li>P2P architectures offer powerful approaches for solving the seemingly intractable problems of the Web and creating a more efficient and robust Internet. </li></ul><ul><li>Creates the most significant challenges to the traditional centralized IT departments. </li></ul><ul><li>Source: O’Reilly: Peer-to-Peer and Web Services Conference, November 5-8, Washington, DC. P2P 2001 Networking Overview. </li></ul>
  59. 59. 8. Contact Information <ul><li>Brand Niemann, Ph.D. </li></ul><ul><ul><li>USEPA Headquarters, EPA West, Room 6143D </li></ul></ul><ul><ul><li>Office of Environmental Information, MC 2822T </li></ul></ul><ul><ul><li>1200 Pennsylvania Avenue, NW, Washington, DC 20460 </li></ul></ul><ul><ul><li>202-566-1657 </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>EPA: http://161.80.70.167 </li></ul></ul><ul><ul><li>Outside EPA: http://130.11.44.140 </li></ul></ul>

×