Universal Access Niemann71602

50 %
50 %
Information about Universal Access Niemann71602
Education

Published on January 17, 2008

Author: Bina

Source: authorstream.com

Removing Barriers with XML Web Services Universal Access Collaboration Expedition Workshop #15 National Science Foundation, Ballston, VA:  Removing Barriers with XML Web Services Universal Access Collaboration Expedition Workshop #15 National Science Foundation, Ballston, VA Brand Niemann XML Web Services Solutions Architect Office of Environmental Information US Environmental Protection Agency July 16, 2002 Overview:  Overview 1. Enterprise Architecture 2. Content Accessibility and Usability 3. Integration of Content Networks 4. Blue Pages Pilot to “Our E-Gov Project” 5. Innovation Diffusion 6. Contact Information 1. Enterprise Architecture:  1. Enterprise Architecture 1.1 Basic Definitions 1.2 E-Government Initiatives 1.3 EPA Enterprise Architecture Program 1.4 XML Web Services 1.5 Architecture of An EPA XML Web Service 1.1 Basic Definitions:  1.1 Basic Definitions Enterprise architecture – a description, in useful models, diagrams, and narrative, of the mode of operation for an enterprise (agency): Logical terms – interrelated business processes and business rules, information needs and flows, and work locations and users. Technical terms – hardware, software, data, communications, and security attributes and standards. 1.1 Basic Definitions:  1.1 Basic Definitions 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. 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. Source: GAO Report on Challenges in Managing and Preserving Electronic Records, June 2002, page 28. 1.2 E-Government Initiatives:  1.2 E-Government Initiatives 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. 1.2 E-Government Initiatives:  1.2 E-Government Initiatives 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: 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. 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. Source: E-Government Strategy, February 27, 2002. 1.2 E-Government Initiatives:  1.2 E-Government Initiatives Portfolios: Government to Citizen (G2C) (5): E.g., Recreation One-Stop Government to Business (G2B) (5): E.g., Business Compliance One-Stop Government to Government (G2G) (5): E.g., Geospatial Information One-Stop Internal Effectiveness and Efficiency (IEE) (8): E.g., E-Records Management Cross-cutting: e-Authentication Infrastructure: Federal Enterprise Architecture Source: http://egov.gov/egovreport-3.htm 1.2 E-Government Initiatives:  1.2 E-Government Initiatives 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. 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. 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. 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. Source: Measuring e-gov, Federal Computer Week, April 8, 2002, pp 20-21. 1.3 EPA Enterprise Architecture Program:  1.3 EPA Enterprise Architecture Program Dedicated staff: Chief Architect and eight Team Members. 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. Completion of a draft baseline architecture assessment for the Environmental Information Architecture business domain. Incorporated a large number of modeling and analysis tools in the baseline applications inventory. Suggested that it include XML Web Services. Source: EPA Enterprise Architecture, Quarter 2, Fiscal Year 2002(Jan-Mar 2002). 1.4 XML Web Services:  1.4 XML Web Services Why XML?: 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/). XML “future proofs” content against periodic technology changes. 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/). 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). 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). 1.4 XML Web Services:  1.4 XML Web Services What is XML?: XML is a standard for preserving and communicating information – encoding, tagging, and internationalizing – that will be everywhere. Web Services provide communication between applications running on different Web servers that will bring the Internet to its new level. XML Web Services are applications running on different devices that communicate XML data using XML messages. XML Web Services for geospatial data use the OpenGIS Consortium’s GML (Geography Markup Language) and OWS (Open Web Services) standards and specifications. Web Services can and should be interoperable across multiple vendor tools and platforms in the enterprise (see http://www.ws-i.org/Community.aspx). 1.4 XML Web Services:  1.4 XML Web Services 1.4 XML Web Services The Web Services Standards “stack”:  1.4 XML Web Services The Web Services Standards “stack” Commonly used by the major vendors: Work Flow (WFDL-Work Flow Description Language). Publication and Discovery (UDDI-Universal Description, Discovery, and Integration). Service Description (WSDL-Web Services Description Language). Messaging (XMLP-XML Protocol from SOAP-Simple Object Access Protocol). Content (XML-Extensible Markup Language). Transport (HTTP-Hypertext Transport Protocol). 1.4 XML Web Services:  1.4 XML Web Services XML.Gov, June 19, 2002: E-Gov Solutions Architects Working Group (SAWG), Federal Enterprise Architecture – Program Management Office: The usage of XML, Web Services, UDDI, SOAP, etc. (Lead-Marion Royal, Co-Chair XML Working Group) Leveraging emerging technologies and industry-proven standards (J2EE, MS.NET, XML, XML Web Services) Assignment of a Solution Architect to each of the 24 e-Gov initiatives. XML Registry/Repository – Business Case Analysis: Booz Allen Hamilton complete the A-11 Exhibit 300 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). XML Web Services Working Group Proposed: Natural role for Government as a provider of raw data in standard format (XML) to private sector, who add value. 1.4 XML Web Services:  1.4 XML Web Services Software Development Lifecycle Models: Classical Software Development: 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. Modern XML Software Development: 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). Source: XML Spy Integrated Development Environments, White Paper, 18 pp., 2002 (http://www.xmlspy.com) 1.4 XML Web Services:  1.4 XML Web Services 1.4 XML Web Services:  1.4 XML Web Services Document Framework Design – Advanced XML Application Development: 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. 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.). 1.4 XML Web Services:  1.4 XML Web Services Document Framework Design – Advanced XML Application Development (continued): 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. 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.) 1.5 Architecture of An EPA XML Web Service:  1.5 Architecture of An EPA XML Web Service Enter your zip code to retrieve environmental information about your community: 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. 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. 1.5 Architecture of An EPA XML Web Service:  1.5 Architecture of An EPA XML Web Service 1.5 Architecture of An EPA XML Web Service http://www.epa.gov/ceppo/lepclist.htm:  1.5 Architecture of An EPA XML Web Service http://www.epa.gov/ceppo/lepclist.htm 1.5 Architecture of An EPA XML Web Service http://www.filemaker.com/xml/:  1.5 Architecture of An EPA XML Web Service http://www.filemaker.com/xml/ 1.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=:  1.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= 1.5 Architecture of An EPA XML Web Service http://130.11.53.73/brand.vxml:  1.5 Architecture of An EPA XML Web Service http://130.11.53.73/brand.vxml 1.5 Architecture of An EPA XML Web Service http://studio.tellme.com/:  1.5 Architecture of An EPA XML Web Service http://studio.tellme.com/ 1.5 Architecture of An EPA XML Web Service 1-866-745-7735:  1.5 Architecture of An EPA XML Web Service 1-866-745-7735 Welcome to the E. P. A. Local Emergency Planning Committee finder. Please speak or touch-tone your 5 digit Zipcode. 84040 Here are results for the Zipcode 84040. 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. Thank You for calling, goodbye. 2. Content Accessibility and Usability:  2. Content Accessibility and Usability What are some of the issues?: 2.1 PDF and Public Documents Public Goods and Services that Work for All* Bridging the Digital Divide and Providing Universal Access* What are some solutions?: 2.2 eXtensible Indexing Language (XIL) for Large PDF Collections Repurposing PDF files into XML Documents* XML “Data Island” Tables* Content Management for Accessibility and Usability* Digital Talking Books with SMIL* Natural Language Interface to Web Content* *Improving Critical Public Information Channels: Speech and Voice Technology for Military and Government Applications Swissotel Washington, Washington, DC, July 30-31, 2002. 2.1 PDF and Public Documents:  2.1 PDF and Public Documents We applaud the efforts that Adobe has made to embrace XML technologies that provide open source, non-proprietary formats. We call on Adobe and other developers to commit to accessible XML practices, as defined by the XML Accessibility Guidelines (XAG) currently in public draft. Janina Sajka, Director, Technology Research and Development, American Foundation for the Blind, and Joe Roeder, Senior Access Technology Specialist, National Industries for the Blind, PDF and Public Documents: A White Paper, Version 1.1, published April 25, 2002. http://www.afb.org/AboutPDF.asp 2.2 eXtensible Indexing Language (XIL) for Large PDF Collections http://www.epa.gov/owow/oceans/nccr/index.html:  2.2 eXtensible Indexing Language (XIL) for Large PDF Collections http://www.epa.gov/owow/oceans/nccr/index.html National Coastal Condition Report: The Problem: Large PDF files (14) totaling 114.6 MB! Files range in size from 0.1 – 17.2 MB. Pages slow to render and print (200+ pages) because of multi-colored backgrounds, graphics, and photographs. Lots of data graphics, but few data tables. Neither a structured – table of contents PDF file nor in ‘Tagged” format for export to XML. The Solution: NXT 3 makes search and display across the entire collection of files very efficient and fast because of XML. http://www.epa.gov/owow/oceans/nccr/index.html 2.2 eXtensible Indexing Language (XIL) for Large PDF Collections:  2.2 eXtensible Indexing Language (XIL) for Large PDF Collections 2.2 eXtensible Indexing Language (XIL) for Large PDF Collections:  2.2 eXtensible Indexing Language (XIL) for Large PDF Collections 3. Integration of Content Networks:  3. Integration of Content Networks 3.1 Background 3.2. Earth 911 3.3 National Environmental Information Exchange Network 3. 4. National Environmental Health Tracking Network 3.5 EPA-State Content Network Pilot 3.6 Paradigm Shifts 3.1 Background:  3.1 Background “Government should stop looking at the number of portals they can put up and rely on a few private channels to provide information to the public” (Stephen Goldsmith, e-gov advisor to President Bush, April 16, 2002). With the proliferation of portals, the Gartner Group has coined the term “Uber Portal” for a portal that sits on top of the portals (The Gartner Group, Emerging Internet Technologies, Local Briefing, June 27, 2001, page 19). Peer-to-peer* content networks provide a way for users to simultaneously access Internet sites, databases, intranets and other formal or informal content resources as if the content existed in a single location. (Andy Warzecha, The META Group, 3/12/2002) With all the portals, “Uber Portals”, and content networks being built, let’s make sure they are interoperable and not just more silos of replicated, warehoused, and/or disconnected information repositories (the author). *Peer-to-peer: Every device connected to the network is both a server and consumer of content. 3.2 Earth 911:  3.2 Earth 911 Started in Arizona in 1991. Recognized by EPA and others in 1995 with a Presidential Environmental Technology Initiative grant to expand nationwide dubbing it “Earth’s 911”. 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. 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). 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. 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. The Earth 911 Foundation is a 501 (c) 3 non-profit organization with a staff of about 40 support by grants and contributions. 3.2 Earth 911:  3.2 Earth 911 3.2 Earth 911:  3.2 Earth 911 3.3 National Environmental Information Exchange Network:  3.3 National Environmental Information Exchange Network “Blueprint for a National Environmental Exchange Network” by the National Blueprint Team released in the spring of 2001 which recommended: the exclusive use of XML as the common basic interchange language for data flows; and simplified versions of the tools (e-commerce servers), technologies (XML), and security levels be applied to the business of environmental agencies. An Implementation Plan was approved by the State/EPA Information Management Workgroup in February 2002. A Network Steering Board has been established and $25 million in grants are about to be awarded to start building the network. A large contract has been awarded to build EPA’s node on the network called Central Data Exchange. The initial focus is on the submission of about 1M standardized XML data files from the states per year. 3.3 National Environmental Information Exchange Network:  3.3 National Environmental Information Exchange Network 3. 4. National Environmental Health Tracking Network:  3. 4. National Environmental Health Tracking Network Significant funding is being made available to states and tribes that will contribute and exchange of environment and public health data as follows: The U.S. Department of Health and Human Services (HHS) are providing $1.1 billion in funding to prepare for bioterrorist attacks. EPA is providing $25 million in grants funds to participate in building the National Environmental Information Exchange Network (The Exchange Network). The Center for Disease Control and Prevention (CDC) and the Agency for Toxic Substances and Disease Registry (ATSDR) plan to provide about $12.5 million for state pilots to develop an Environmental Health Tracking Network. 3.5 EPA-State Content Network Pilot:  3.5 EPA-State Content Network Pilot Started by EPA within FedStats in the fall of 2000– a loose interagency umbrella for about 70 agencies and about 200 programs that produce Federal statistics. Continued under the auspices of the CIO Council’s XML Working Group as the FedGov Content Network. Extended to EPA Program Offices, Regions, and States as part of the author’s XML Web Services Training and Pilot Projects. Recently received special Quad Council award for innovation for use of XML and VoiceXML. Uses the NextPage NXT 3 P2P Platform and the Tellme Networks infrastructure (see next slides). 3.5 EPA-State Content Network Pilot:  3.5 EPA-State Content Network Pilot NextPage NXT 3 P2P* Platform: Andy Warzecha, The META Group, 3/12/2002: “If companies want to do cross-enterprise content management, NextPage has the solution”: "Content networks provide a way for users to simultaneously access Internet sites, databases, intranets and other formal or informal content resources as if the content existed in a single location." "The advantage of this approach is that new content sources can be added quickly ... This puts power in the hands of business users to quickly tie in or disconnect the various content sources they require access to." (see next slide) * Peer-to-peer: Every device connected to the network is both a server and consumer of content. 3.5 EPA-State Content Network Pilot:  3.5 EPA-State Content Network Pilot 3.5 EPA-State Content Network Pilot:  3.5 EPA-State Content Network Pilot NextPage NXT 3 P2P Platform: Esther Dyson’s Release 1.0, 1/22/2002: “NextPage is unique in the content-management market in its distributed approach”: “NetxPage’s platform, NXT 3, virtually connects the distributed information sources and makes them appear integrated to the user. Unlike syndication, in which content is copied and integrated with other content locally, NextPage keeps objects where they are.” “NextPage uses the standard simple object access protocol (SOAP) to exchange and normalize information between local content directories, assembling meta-indexes so that users can search or manipulate content transparently, regardless of physical location.” 3.5 EPA-State Content Network Pilot NXT 3 Platform Architecture and Services (SCOTS*):  3.5 EPA-State Content Network Pilot NXT 3 Platform Architecture and Services (SCOTS*) *Standards-based Commercial Off-the-Shelf Software 3.5 EPA-State Content Network Pilot Build Your Own Enterprise Architecture!:  3.5 EPA-State Content Network Pilot Build Your Own Enterprise Architecture! 3.5 EPA-State Content Network Pilot Submit and Manage Distributed Content:  3.5 EPA-State Content Network Pilot Submit and Manage Distributed Content 3.5 EPA-State Content Network Pilot A Content Node for Every EPA Office, Program, Region, State & Partner:  3.5 EPA-State Content Network Pilot A Content Node for Every EPA Office, Program, Region, State & Partner 3.6 Paradigm Shifts XML Separates Content from Presentation:  3.6 Paradigm Shifts XML Separates Content from Presentation Content Presentation Traditional Content Network: Integrated Portal Content Network: “Uber” Portal Personalization: Customer Relationship Management Centralized Distributed Centralized Distributed 3.6 Paradigm Shifts XML Meta Data Matrix:  3.6 Paradigm Shifts 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. 3.6 Paradigm Shifts XML Meta Data Architecture:  3.6 Paradigm Shifts XML Meta Data Architecture XML data and meta data architectures are connected. From a Resource Perspective, meta data is either external to or embedded within the data. From a Client Perspective, meta data is either centralized or distributed. 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. 3.6 Paradigm Shifts XML Meta Data Architecture:  3.6 Paradigm Shifts XML Meta Data Architecture Client-server approaches to meta data work when there are a small number of known sources of meta data. Peer-to-peer approaches are needed in an more distributed environment to simultaneously query, discover, and aggregate the results locally. The architecture of peer-to-peer systems is instructive in the design of meta data applications using distributed external meta data. 3.6 Paradigm Shifts “Hierarchical Peer-to-Peer” Diagram:  3.6 Paradigm Shifts “Hierarchical Peer-to-Peer” Diagram Key: Client Nodes (outer circles); Server Nodes (inner circles) 3.6 Paradigm Shifts “Hierarchical Peer-to-Peer” Diagram:  3.6 Paradigm Shifts “Hierarchical Peer-to-Peer” Diagram Centralized meta data sources pass queries from server to server on behalf of a particular client. 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. Any given client node must know the address of the server node which forms its point of contact for the network. 3.6 Paradigm Shifts “True Peer-to-Peer” Diagram:  3.6 Paradigm Shifts “True Peer-to-Peer” Diagram Key: Peer Nodes (all circles) 3.6 Paradigm Shifts “True Peer-to-Peer” Diagram:  3.6 Paradigm Shifts “True Peer-to-Peer” Diagram Makes each networked client a server of the meta data that it has aggregated from its local machine. 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. This form of distributed meta data architecture is expected to become more prevalent. 3.6 Paradigm Shifts “PIE:” Presence, Identity, and Edge Resources:  3.6 Paradigm Shifts “PIE:” Presence, Identity, and Edge Resources Resources at the Center migrate to the Edge, anonymous users gain Identity, and transient connectivity yields to Presence. 3.6 Paradigm Shifts “PIE:” Presence, Identity, and Edge Resources:  3.6 Paradigm Shifts “PIE:” Presence, Identity, and Edge Resources The third generation of the Internet. P2P architectures offer powerful approaches for solving the seemingly intractable problems of the Web and creating a more efficient and robust Internet. Creates the most significant challenges to the traditional centralized IT departments. Source: O’Reilly: Peer-to-Peer and Web Services Conference, November 5-8, Washington, DC. P2P 2001 Networking Overview. 4. Blue Pages Pilot to “Our E-Gov Project”:  4. Blue Pages Pilot to “Our E-Gov Project” 4.1 What is the Blue Pages Project? 4.2 What is the “Blue Pages” Pilot Project? 4.3 Our E-Gov Project: Government Phone Directories. Translating Print Listings into an Interactive Phone Service for Intelligence Gathering, Public Utility & Performance Benchmarking: Speech and Voice Technology for Military and Government Applications, Swissotel Washington, Washington, DC, July 30-31, 2002. 4.1 What is the Blue Pages Project?:  4.1 What is the Blue Pages Project? Recipient of the Hammer Award in 1996: 24 agencies and 200 federal employees working on a 3-year project to make federal listings (phone, FAX, and Web sites) in the local phone directories—called “blue pages”—more user friendly in 10 cities (18,546,000 households). National Performance Review Report “The Best Kept Secrets in Government” (VP Gore, September 1996): Page 35, “Number, Please”: “The low-tech puzzle that must be solved before reaching the high-tech government is the “blue pages”. Facts: Citizens used the blue pages 81 million times per year. Research indicates that 25% of the citizens give up when they can’t reach the right office. Government estimates that rerouting calls costs $10. Currently there are 6,200 telephone directories in the US. 4.1 What is the Blue Pages Project?:  4.1 What is the Blue Pages Project? http://bp.fed.gov/ Print 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? What is the “Blue Pages” Pilot Project?: Visionary Goals for the Blue Pages (Owen Ambur): Use agency databases, gather and maintain with e-forms, geo-reference, provide access by Web and telephone, and include Frequently Asked Questions and Documents: 1-800 Say-The-Word: The X.500 Blue Pages Key to Stockholder/Customer-Accessible Government (12/13/97): http://users.erols.com/ambur/BluePage.html Additional Requirements for the Blue Pages Data Collection & Maintenance System (11/2/98): http://users.erols.com/ambur/bluepgs.html Apply the same Quad Council Award winning XML Web Services technology to the Government’s phone directories: http://www.gcn.com/21_7/news/18303-1.html http://www.fcw.com/fcw/articles/2002/0318/cov-tech2-03-18-02.asp 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? Search Form: XML Output: 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? Search Form: Web Output: 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? “Ideal” Blue Pages database (877-728-8355): S: Welcome to the US Government Blue Pages Directory – Your one stop directory for government services in your local area. S: Please say the city and state you'd like information for, or hang on, while I get information for | Washington, DC. U: Las Vegas, Nevada S: OK, Las Vegas, Nevada. Here are your choices. When you hear the one you want, just say it. S: Agriculture, Commerce, Courts, Defense, Education, Emergency Services, Energy, Environment, Immigration & Customs, Law Enforcement, Parks & Recreation, Health… U: Health S: Here's a list of choices in Health. When you hear the one you want, just say it. S: AIDS hotline, Adoption, Cancer Treatments, Child Safety, Drug & Alcohol Treatment… U: AIDS hotline S: The phone number for | the national AIDS hotline is | 800 342 2437. | Once again, the phone number is | 800 342 2437. Etc. 4.2 What is the “Blue Pages” Pilot Project?:  4.2 What is the “Blue Pages” Pilot Project? What are the next steps? (generic as well): 1. Scalability - use the complete database to demonstrate the XML Web Services platforms will scale to provide a portal. 2. Distribute-ability - use an extract of the database for an individual agency (i.e. GSA and EPA) to demonstrate live distributed updating from a node integrated with the main portal. 3. Interoperability - demonstrate that XML outputs from two or more vendor platforms can be exchanged. (Rationale: Final deployment will probably not be a single vendor and at least two or three alternatives will be necessary before the market is likely to be convinced that the relevant standards are ready for prime time usage.) 4. Multi-channel dissemination-ability – besides HTML and XML, demonstrate print, telephone and other modes of delivery. 4.3 My E-Gov Project: Government Phone Directories:  4.3 My E-Gov Project: Government Phone Directories 4.3.1 Use FirstGov.Gov to Locate Myself: Reference: Phone Directories U.S. Government Telephone and E-Mail Directories Federal White Pages (first choice) Agency Phone Directories by Organization (second choice) EPA Directory 4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories: Inventory Repurpose Demonstrate Work Left to Do 4.3.1 Use FirstGov.Gov to Locate Myself Federal White Pages: It is out of date! How do I fix it?:  4.3.1 Use FirstGov.Gov to Locate Myself Federal White Pages: It is out of date! How do I fix it? 4.3.1 Use FirstGov.Gov to Locate Myself Environmental Protection Agency http://www.epa.gov/epahome/locator.htm:  4.3.1 Use FirstGov.Gov to Locate Myself Environmental Protection Agency http://www.epa.gov/epahome/locator.htm 4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories:  4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories Content types: Files (PDF, Excel, etc.) Web (HTML, etc.) Databases (Oracle, Access, etc.) Conversion to XML: XML Data Islands within HTML files eXtensible Indexing Language (XIL)* for proprietary formats RDBMS-to-XML Content Adapter* Integrate with XML Web Services*: Hierarchical system of content folders on one or more servers Content submitted and managed remotely or centrally Couple with VoiceXML: Possible database repurposing Tools and testing* *Standards-based Commercial Off-the-Shelf Software (SCOTS) 4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories:  4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories 4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories:  4.3.2 Use XML and VoiceXML Web Services for Government Telephone Directories Specific near-term tasks: Create XML Data Islands or RDBMS-to-XML for other major agency directories . Include more geo-referenced content like LandView 5 in support of the E-Gov Geospatial Information One-Stop Initiative. Add distributed updating of directory content. Add custom XML Stylesheets (XSLT and XSLT/FO) for different internal and external Web versions and printing with PDF. Add State and local nodes using the Earth 911 model of public-private partnerships (http://earth911.org). Improve XML database for VoiceXML (semantics, what we do in the government, etc. - might ultimately be part of E-Gov Authentication Initiative). The future: Government Directories become like the 1-800-555-1212 AT&T Directory Assistance. FirstGov becomes a VoiceXML Portal like 1-800-555-TELL. 5. Innovation Diffusion:  5. Innovation Diffusion 5.1 Goals 5.2 Specific Examples: 5.2.1 Federal Webmasters Conference, May 20th 5.2.2 Small Business Administration, June 18-20th 5.2.3 West Virginia Department of Environmental Protection, July 9-11th 5.1 Goals:  5.1 Goals To bring you the best: Video Introductory book Tools Pilot Projects XML experts 5.2.1 Federal Webmasters Conference, May 20th:  5.2.1 Federal Webmasters Conference, May 20th To bring you the best: Video: Made a video for distribution. Introductory book: Handouts and Web site. Tools: NextPage’s NXT 3 Pilot Projects: NXT 3 on diverse agency content. XML experts: Janina Sajka, Director, Technology Research and Development Governmental Relations Group, American Foundation for the Blind and Chris Tucker, CEO and Founder, Ionic Enterprise (GML and Open Web Services for Geospatial Data) 5.2.1 Federal Webmasters Conference, May 20th:  5.2.1 Federal Webmasters Conference, May 20th Preface: This tutorial is being videotaped by Susan Turnbull (GSA) for use in the Instant Access software at the Universal Access Collaboration Workshop on July 16th. Part 1 (9 a.m.-12 noon): XML (eXtensible Markup Language): 9-10:15. VoiceXML (XML for the telephone): 10:30-11:15. GML (XML for geospatial databases): 11:15-11:45. Questions and Answers: 11:45-12. Part 2 (1-4 p.m.): Web Content Management Strategies, Tools and Best Practices (Howard McQueen). 5.2.1 Federal Webmasters Conference, May 20th:  5.2.1 Federal Webmasters Conference, May 20th 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 5.2.1 Federal Webmasters Conference, May 20th:  5.2.1 Federal Webmasters Conference, May 20th Notes on schematic diagram: GML makes it possible to render legacy and third-party data and services interoperable – minimizing the coupling between components – by “wrapping” existing systems. The forthcoming GML 3.0 will include support for SML (Sensor Modeling Language) for real-time spatial data network data streams. Geospatial objects can be created, updated, and/or deleted through the Web Browser and Mobile/Wireless Devices. 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). 5.2.1 Federal Webmasters Conference, May 20th:  5.2.1 Federal Webmasters Conference, May 20th 5.2.2 Small Business Administration, June 18-20th:  5.2.2 Small Business Administration, June 18-20th To bring you the best: Video: Introduction to XML. Introductory book: XML Step by Step (Second Edition). Tools: XML Spy 4.4 Suite. Pilot Project: NXT 3 on diverse content for e-Gov Business Compliance One-Stop. XML expert: Lee Gibbons, Director, Product Strategy, NextPage, The Future of Distributed Content Management. 5.2.2 Small Business Administration, June 18-20th:  5.2.2 Small Business Administration, June 18-20th Tuesday, June 18: Morning (10-noon) Introductions and Logistics Unit 2. Introduction to XML Video Questions and Answers Tuesday, June 18: Afternoon (1-3 p.m.) Install and Use XML Spy 4.4 IDE Unit 3a: XML Step-by-Step, Second Edition (Highlights) Wednesday, June 19: Morning (10-noon) Unit 3a: XML Step-by-Step, Second Edition (Highlights continued) Wednesday, June 19: Afternoon (1-3 p.m.) Unit 5: XML Spy Tutorial Unit 25: XML Web Services: SBA Content (Office XP-Word, Excel, and Access, and Publications and Forms) Thursday, June 20: Morning (10-noon) Unit 25: XML Web Services: SBA Content (continued) Thursday, June 20: Afternoon (1-3 p.m.) NextPage Enterprise Content Networking and Matrix 5.2.2 Small Business Administration, June 18-20th:  5.2.2 Small Business Administration, June 18-20th 5.2.2 Small Business Administration, June 18-20th:  5.2.2 Small Business Administration, June 18-20th 5.2.2 Small Business Administration, June 18-20th:  5.2.2 Small Business Administration, June 18-20th Thanks so much for the wonderful training you provided our OCIO staff.  It was not only educational, but inspirational.  I am a true advocate now of XML.  I've begun to enhance several project and am talking to several SBA program offices about possible uses. I have asked our Business Compliance One-Stop project manager to contact you on possible solutions for his e-gov initiatives.   I especially think he needs to learn about uberportals, since he will be using information from many federal, state and local web sites. I would like to contact you soon as well, to see if you can provide input for a couple of our key tasks as well.  Again - thanks for the great class.  You did an outstanding job. Diane Gannon, Director, Productivity Enhancement Staff, Office of the Chief Information Officer. 5.2.3 West Virginia Department of Environmental Protection, July 9-11th:  5.2.3 West Virginia Department of Environmental Protection, July 9-11th To bring you the best: Video: Introduction to XML. Introductory book: XML Step by Step (Second Edition). Tools: XML Spy 4.4 Suite (with Oracle 91 R2). Pilot Projects: NXT 3 on diverse content and XML Spy with Oracle. XML experts: Kevin Williams (pre-eminent XML author and developer and Charles Town, WV, neighbor). 5.2.3 West Virginia Department of Environmental Protection, July 9-11th:  5.2.3 West Virginia Department of Environmental Protection, July 9-11th XML Schemas enable translations from Objects to XML Documents, and from XML Documents to databases (and vice-versa). 5.2.3 West Virginia Department of Environmental Protection, July 9-11th:  5.2.3 West Virginia Department of Environmental Protection, July 9-11th Figure 2 : Data-Oriented Access 5.2.3 West Virginia Department of Environmental Protection, July 9-11th:  5.2.3 West Virginia Department of Environmental Protection, July 9-11th Tuesday, July 9th: 9-12 noon - Session 1: Introduction to XML (90 minute video). 12-1 p.m. - Lunch Hour 1-4 p.m. - Session 2: Install XML Spy 4.4 and do XML Step-by-Step (highlights) (Need your own SPY key code and install CD-ROM files) 4-5 Further discussions and one-on-one help. Wednesday, July 9th 9-12 noon - Session 3: Complete XML Step-by-Step and do XML Spy 4.4 Tutorials 12-1 p.m. - Lunch Hour 1-4 p.m. - Session 4: XML Schemas and Relational Databases 4-5 Further discussions and one-on-one help. Thursday, July 10th (to be assisted by Kevin Williams at no cost) 9-12 noon - Session 5: Review of Information Provided 12-1 p.m. - Lunch Hour 1-3 p.m. - Session 6: Discussion of XML-based Systems and Traditional RDBMS Systems (the advantages and disadvantages of each and their integration) 3-4 p.m. - Further discussions and next steps (NEIEN node, etc.) 6. Contact Information:  6. Contact Information Brand Niemann, Ph.D. USEPA Headquarters, EPA West, Room 6143D Office of Environmental Information, MC 2822T 1200 Pennsylvania Avenue, NW, Washington, DC 20460 202-566-1657 niemann.brand@epa.gov EPA: http://161.80.70.167 Outside EPA: http://130.11.44.140

Add a comment

Related presentations

Related pages

Removing Barriers with XML Web Services Universal Access ...

Removing Barriers with XML Web Services Universal Access 1 . Removing Barriers with XML Web Services Universal Access Collaboration Expedition Workshop #15
Read more

How to advocate Open Access repositories more successfully

How to advocate Open Access repositories more ... Services Universal Access We look to the LEPC ... gov/Universal%2520Access-Niemann71602.ppt.
Read more

The Future of the Web: Visual, Social, Universal | PPT ...

The Future of the Web: Visual, Social, Universal The Future of the Web: Visual, Social, Universal Ben Shneiderman (ben@cs.umd.edu) Director, Human-Computer
Read more