XML Data Exchange Across Multiple Levels of Government Using Native XML Databases

1
XML Data Exchange Across Multiple Levels of
Government Using Native XML Databases

• Pilot Project Overview by Brand Niemann
• Chair, CIO Councils XML Web Services Working
  Group
• April 28, 2003

2
Overview

• 1. The CIO Councils Architecture and
  Infrastructure Committee
• 2. XML Web Services Working Group
• 3. Pilot Project
• 4. Tamino XML Server
• 5. Contact Information

3
1. The CIO Councils Architecture and
Infrastructure Committee

• Leadership
• John Gilligan, USAF CIO, Co-Chair.
• Laura Callahan, DHS Deputy CIO, Co-Chair.
• Norman Lorentz, OMB CTO, Advisor.
• Three Subcommittees
• Governance Policy guidance and assistance in
  design and implementation of the Enterprise
  Architecture discipline and practice.
• Robert Haycock, OMB, and John Przysucha, DOE.
• Components Identify, mature and facilitate
  use/reuse of Component-based Architectures.
• Reynolds Cahoon, NARA, and Robert Haycock, OMB.
• Emerging Technology Identify technologies with
  the potential to improve the value and quality of
  the FEA.
• Dawn Meyerriecks, CTO, DISA, and Mark Day, EPA,
  DCIO.

4
1. The CIO Councils Architecture and
Infrastructure Committee

• Emerging Technology Subcommittee
• Purpose
• A group of working groups that identifies
  technologies that support the Federal Enterprise
  Architecture (FEA) and E-Government Programs.
• Deliverables
• Regular open meetings, workshops, etc.
• An incubator process of pilots to develop
  components (see next slide for definition) for
  the Governance and Components Subcommittees.
• Leadership
• Leaders of the Federal PKI Steering Committee,
  XML, XML Web Services, and Universal Access
  working groups.

5
1. The CIO Councils Architecture and
Infrastructure Committee
Leadership

• Chairs
• Judith Spencer, GSA
• Owen Ambur, DOI, and Marion Royal, GSA
• Brand Niemann, EPA
• Susan Turnbull, GSA

• Working Group
• Federal PKI Steering Committee
• XML
• XML Web Services
• Universal Access

6
1. The CIO Councils Architecture and
Infrastructure Committee

• Emerging Technology Subcommittee
• Recent AIC Guidance
• The Subcommittee needs a plan for evolution to
  meet near and longer term expectations.
• An Enterprise Architecture component is defined
  as a self-contained business process or service
  with predefined functionality that may be exposed
  through a business or technology interface.
• Work Plan
• Baseline October 2002 to present.
• Transition Next 1-3 months.
• Target Next 3-6 months.
• Pilot Selection and Graduation Criteria and
  Process
• Tools
• Collaboration (with other Subcommittees -
  CollabNet Enabling collaborative software
  development strategies and communities).
• Clearinghouse (Find and Filter Pilot Proposals
  with XML-based forms - part of the Eforms for
  E-Gov Pilot).
• Registries and Repositories (Common Content
  Linked by XML Web Services).

7
1. The CIO Councils Architecture and
Infrastructure Committee
Baseline October 2002 to present

• Working Group
• Federal PKI Steering Committee
• XML
• XML Web Services
• Universal Access

• Deliverables
• AIC graduated it to the Components SC.
• XML Registry focus.
• 12 Incubator Pilots.
• Regular Workshops and e-Gov Conferences.

8
1. The CIO Councils Architecture and
Infrastructure Committee
Transition Next 1-3 months

• Working Group
• XML
• XML Web Services
• Universal Access
• Technology Life-Cycle Process

• Deliverables
• Plan for moving XML Registry to the Components
  SC.
• Graduate successful pilots to the Governance and
  Components SCs.
• Regular Workshops and Technology Conferences.
• Develop process and tools.

9
1. The CIO Councils Architecture and
Infrastructure Committee
Target Next 3-6 months

• Working Group
• XML
• XML Web Services
• Universal Access
• Technology Life-Cycle Process

• Deliverables
• XML Registry becomes part of the Components SC.
• Graduate additional successful pilots to the
  Governance and Components SCs.
• Regular Workshops and Technology Conferences.
• Initiate process and tools.

10
2. XML Web Services Working Group

• Chartered by the Federal CIO Council under its
  Architecture and Infrastructure Committee
  (CIOC/AIC)
• Works with the CIOC/AIC, the OMB Solution
  Architects Working Group (SAWG), and the Industry
  Advisory Council (IAC) to produce incubator pilot
  projects in support of the e-Gov Initiatives that
  use XML Web Services to demonstrate increased
  accessibility and interoperability.
• See http//web-services.gov for definitions and
  purpose.
• Recent Press
• Working group tests tools for Web services,
  GCN,12/16/02 Vol. 21 No. 34.
• http//www.gcn.com/21_34/news/20656-1.html
• Let the building begin, GCN, 1/27/03, Vol. 22,
  No. 2.
• http//gcn.com/22_2/

11
2. XML Web Services Working Group

• Before - XML Web Services Repository/Distributed
  Content Network and VoiceXML
• March 20, 2002, The CIO Council Showcase of
  Excellence, Special Innovation Award, Presented
  to the Environmental Protection Agency, Natural
  Language Interface to Web Content, By the Federal
  Leadership Council (Mark Forman and the Quad
  Council), In Association with Post Newsweek Tech
  Media/FOSE, Washington, DC.
• After CIOC XML Web Services Working Group
• April 1, 2003, Working Group Chair Recognized
  with Emerging Technology/Standards Leadership
  Award at the SecureE-Biz.Net Summit, from Mark
  Forman, Associate Director, IT and eGovernment,
  OMB, and David McClure, VP e-Gov, Council for
  Excellence in Government for ushering in new
  technology to allow us to conduct e-Business
  securely to further implement the Presidents
  Management Agenda.

12
2. XML Web Services Working Group

• 4 of the top 9 priorities of the new XML Web
  Services Working Group are to develop a registry
  and collaboration facility for Web Services in
  support of e-Gov
• 1. Provide direct support on implementing Web
  Services to 24 e-Gov initiatives.
• 2. Maintain registry of WS-related projects or
  efforts, to avoid duplication and promote
  information sharing.
• 3. Implement a registry of available Web Services
  (a loose registry of human-researchable
  information at first, but later supporting
  automated services location).
• 9. Provide on-line collaboration facility for
  exchange of sample business cases, templates, and
  other info related to Web Services.

13
Registries and Repositories in the Federal
Enterprise Architecture Data and Information
Reference Model
Common Content Linked by XML Web Services

• Types of Registries(1)
• ISO 11179Registries
• OASIS/ebXMLRegistries
• UDDIRegistries
• OntologicalRegistries
• Database Catalogs
• Software Component Registries
• CASE Tool Repositories

• Pilot Projects with Registries
• XML Design Collaboration and Registry Platform
• XML Design Collaboration and Registry Platform
• XML Design Collaboration and Registry Platform
  and Tamino
• Open Standard Ontology Tool and Platform (Topic
  Maps)
• Various (MetaMatrix, etc.)
• Various (CollabNets SourceCast, etc.)
• Various (GIDS, etc.)

(1) Source Eliot Christian, USGS, based on work
of ISO/IEC JTC1/SC32 Data Management Subcommittee
chair, Bruce Bargmeyer (NIST, EPA, LBL).
14
2. XML Web Services Working Group

• Users never know what they want
• until they see what they get

15
2. XML Web Services Working Group

• Pilots
• Purpose To populate the Government-wide
  Components Registry and Repository with reusable
  (interoperable) components from successful
  pilots.
• An Enterprise Architecture Component is a
  self-contained business process or service with
  predetermined functionality that may be exposed
  through a business or technology interface.
• Three Step Process
• (1) Identify and Vet in the Working Group.
• (2) Produce the Pilot.
• (3) Operationalize the Successful Pilots.
• Funding Options
• (1) Vendor Resources.
• (2) Agency Resources.
• (3) Combination of (1) and (2).

16
2. XML Web Services Working Group

• Pilot Selection Criteria
• Inherited from previous work
• E.g., Digital Talking Books, VoiceXML, and
  Content Networking.
• Working Group priorities
• E.g., 5 of the top 9 priorities given to the new
  XML Web Services Working Group were to develop a
  registry and collaboration facility for Web
  Services in support of e-Gov.
• Formal request from OMB, FEA-PMO, AIC and
  Subcommittees, etc.
• E.g., Eforms for E-Gov, XML Data Exchange
  Across Multiple Levels of Government Using Native
  XML Databases, etc.
• IAC Web Services SIG recommendation
• E.g., User Customization and Dynamic Discovery.
• Proposed and Vetted in the Working Group
• E.g., Cognitive Topic Map Web Sites.

17
2. XML Web Services Working Group

• Pilot Graduation Criteria
• The AIC Leadership decides it is ready.
• E.g., Federal PKI Steering Committee.
• The Governance and Components Subcommittees
  request a specific component with a specific
  schedule.
• E.g., XML Registry.
• The Emerging Technology Subcommittee Co-Chairs
  and Working Group Leaders agree it is ready.
• E.g., The Technology Life Cycle process.
• The Working Group leaders set a schedule for the
  pilots.
• E.g., XML Web Services Working Group.

18
2. XML Web Services Working Group

• Current Pilot Process
• OMB wants IAC to lead by example by
  implementing enterprise architecture principles
  in their own businesses and open standards in
  their own products, but OMB cannot fund IAC.
• IAC wants to influence the FEA process and market
  implementation of component-based architectures
  in their products and services.
• IAC has mirrored the AIC structure and wants to
  do pilots which have the following benefits to
  both IAC and the AIC
• Vendors are indoctrinated in the FEA and their
  pilot proposals are vetted within their own SIGs.
• The proposed pilots represent a consensus
  recommendation from the SIGs.
• The proposed pilots are ready to be matched to
  real needs and demonstrated more rapidly than
  just solutions in search of problems.
• Usually, proposed pilots need to be attached to
  either the IAC, an E-Gov Initiative, agency, or
  sponsoring organization to be viable since
  unattached pilots are difficult to foster and
  resource.

19
2. XML Web Services Working Group

• Pilot Titles
• 1. Digital Talking Books on CD-ROM and the Web as
  VoiceXML.
• 2. XML Collaborator.
• 3. VoiceXML for Universal Access and Homeland
  Security Applications.
• 4. Geospatial Interoperability.
• 5. XML Web Services Content Authoring,
  Management, and Dissemination.
• 6. Military Systems-Federation of Registries,
  etc.
• 7. E-Forms for e-Gov The Use of XML
  Standards-based Applications.
• 8. The MetaMatrix System for Model-driven
  Integration with Enterprise Metadata.
• 9. Cognitive Topic Map Web Sites-Aggregating
  Information Across Individual Agencies and E-Gov
  Initiatives.
• 10. Collaboration and CoSourcing Designing
  Intergovernmental Services and Sharable
  Components.
• 11. The Potential of Semantic Technologies for
  E-Gov.
• 12. XML Data Exchange Across Multiple Levels of
  Government Using Native XML Databases.

20
2. XML Web Services Working Group
Schedule

• Pilot Status
• 1. Graduating to GPO/GSA
• 2. Planned Public Release
• 3. Ready for EPA and DHS
• 4. Just Beginning
• 5. Well Underway
• 6. Just Beginning
• 7. Pilot Sub-teams Formed
• 8. Ready for DHS
• 9. Just Beginning
• 10. Just Beginning
• 11. Just Beginning
• 12. Just Beginning

• Planned Date
• April 15th Workshop Report
• May 5th Conference
• April May Presentations
• TBA
• May June Presentations
• TBA
• Interim-June, Final-October
• May 14-15th Presentations
• April 15th Workshop Report
• At Technology Conference
• May 14th Workshop Report
• June 17th Workshop Report

21
2. XML Web Services Working Group

• April 15th Meeting Agenda
• 1. Introduction
• Updates and Announcements.
• Some Coming Attractions.
• 2. Business
• Report on the IAC Web Services SIG.
• Report on the MITRE Web Services SIG Pilot
  Projects.
• Report on Department of Homeland Security Web
  Services Community/Activity.
• 3. Presentations
• Organizations - Organizations Jayne Dutra,
  NASA-JPL, and Joseph Busch, Taxonomy Strategies,
  Proposed Pilot Project Enabling Knowledge
  Discovery Taxonomy Development for NASA.
• Pilot Project - Kevin Williams, Blue Oxide
  Technologies, XML Collaborator with Taxonomies
  and Other Content, in coordination with the XML
  Working Group Meeting on Taxonomies for
  Classification of E-Records, April 16, 2003.
• Pilot Project - Adam Hocek, Broadstrokes, Inc.
  (and Co-author of Definitive VoiceXML), VoiceXML
  Applications.
• Pilot Project Muhannad Kanaan, DynCorp, and
  Team, EPA Facility Data Homeland Security XML and
  VoiceXML Web Services.

22
2. XML Web Services Working Group

• E-Gov Initiatives Being Supported
• G2C
• Recreation One Stop (DOI)
• Gov Benefits (DOL)
• USA Services (GSA)
• G2B
• Online Rulemaking Management (EPA)
• One-Stop Business Compliance (SBA)
• Consolidate Heath Informatics (HHS)
• G2G
• Geospatial Information One-Stop (DOI-OGC)
• eGrants (HHS)
• IEE
• eRecords Management (NARA)
• Other
• Federal Enterprise Architecture (FEA-PMO)
• XML Registry (GSA-NIST)

23
2. XML Web Services Working Group

• New Announcements
• April 10, Working Group Announces Opportunity for
  Vendors Participating in the "E-Forms for E-Gov"
  Pilot to Pilot the Use of XML Web Services in
  E-Gov Initiatives (e.g. e-Grants, One Stop
  Business Compliance, etc.) to Support an
  "Assessment of Readiness" by the Working Group
  for OMB's Solutions Architects Working Group
  (SAWG) and the "QuickWin" Task of the AIC's
  Components Subcommittee. All Vendors invited to
  participate (Adobe-Acrobat 6 and
  Microsoft-InfoPath have expressed interest so
  far).
• Also Opportunity to Present/Demonstrate How the
  New Web Services Security Standards (WS-Security)
  Could Help the E-Gov Initiatives as Suggested
  Recently by Joe Chiusano on March 17th.

24
2. XML Web Services Working Group

• Some Coming Attractions
• April 22, 2003, MITRE XML SIG Technology Spring
  Meeting. XML Web Services Working Group
  Collaboration on Pilots.
• April 30-May 1, 2003, 2nd Annual Speech
  Technology for Government and Military
  Applications Forum. VoiceXML Pilots.
• May 5-7, 2003, FedWeb Spring 03, Tutorial XML
  for Managers Using Pilot Project Tools to Build
  e-Gov Projects and Session "Eforms for E-Gov"
  Pilot Project.
• May 14, 2003, in conjunction with the Universal
  Access Collaboration Workshop 24 at the National
  Science Foundation (Ballston, VA Orange Line
  Metro Station). Agenda in process.
• June 17, 2003, in conjunction with the Universal
  Access Collaboration Workshop 25 at the National
  Science Foundation (Ballston, VA Orange Line
  Metro Station). Agenda in process.
• June 19, 2003 (tentative), Components Technology
  Conference, Washington, DC.

25
3. Pilot Project

• Highlights
• Initiated in January 2003 and presented to
  Working Group on March 4th.
• An Overview of UDDI in Tamino XML Server 4.1 and
  The Tamino WebDAV Server.
• http//www.softwareag.com/corporat/news/dec2002/Ta
  mino_41.htm
• Interest from e-Gov Initiatives (E-Grants,
  Business Compliance One-Stop, etc.) and Agencies
  (EPA Grants, OECA-AFS, OEI-CDX, etc.) during
  January 2003 to present.
• EPA Grants Office discussion of architecting with
  native XML database technology in conjunction
  with CDX (Chris Clark) and IBMs WebSphere (John
  Sullivan). (See next slide.)
• Mapped to the Work Plans and Pilots of the
  Governance and Components Subcommittees in
  January March 2003.
• Announced at FOSE 2003 by Bob Haycock on April
  10th.
• http//www.gcn.com/vol1_no1/daily-updates/21691-1.
  html

26
E-Grants Single System Solution (1/29/03)
XForms Web Browser Interface
Applicant 3
Applicant 2
Applicant 1
..
Applicant N

Valid XML
XML Collaborator Design Collaboration And
Registration Support
E-Grants Trusted Broker
XML Repository Web Services
Valid XML
XML Repository Web Services
Agency N
Agency 1
Agency 2
Agency 3
..
Trusted Broker Embodies Standards, Benefits
Applicants and Agencies Facilitates
System-to-System Interfaces Builds applicant
knowledge of "core" data Helps identify
commonalities among agency-specific data
Annotations by WG Chair
27
3. Pilot Project

• OECA-AFS and CDX Interactions
• Use of Native XML Database Technology suggested
  to CDX, states, and EPA regions in XML Web
  Services Training by myself during 2002.
• Proposal for XML Technology Planning and
  Analysis to OECA-AFS from Software AG in December
  2002.
• Software AG makes me aware of the OECA-AFS
  interest in piloting use of the Tamino XML Server
  in January 2003.
• OECA-AFS interested in being a part (a use case
  with a specific data application) of the XML Web
  Services Working Groups Pilot Project - XML Data
  Exchange Across Multiple Levels of Government
  Using Native XML Databases.
• Discussions with Software AG and OECA-AFS lead to
  a proposed MOU and Proposal for XML
  Proof-of-Concept to OECA-AFS for Pilot Project in
  March 2003.
• Participation in April 23-25, 2003 Tamino Tools
  for Application Development (Short Course).
• CDX (Chris Clark) expresses interest in Tamino
  XML Server for CDX.
• Oracle 9i is expensive and difficult to
  implement (e.g. the mappings from XML to
  relational).

28
4. Tamino XML Server

• 4.1 Concepts
• 4.2 Getting Started
• 4.3 Training and Certification
• 4.4 Online Resources

29
4.1 Concepts

• Tamino XML Server is a high performance data
  management platform based on XML standards built
  to
• Efficiently store XML documents natively (in
  their original format)
• Expose information residing in various external
  XML or non-XML sources (legacy data) or
  applications to the outside world in XML format
  and
• To search and effectively retrieve the
  information Tamino has access to.

Transaction Architecture for the Management of
INternet Objects
30
4.1 Concepts

• Tamino XML Server is
• The first native XML Server!
• Core Services(1) Enabling Services(2)
  Solutions(3)
• Examples of (1) storing documents in native XML
  and non-XML formats (2) WebDAV (Web Distributed
  Authoring and Versioning) from the open source
  developer community and (3) open standards
  open architecture based so new services can be
  added like UDDI.
• APIs (Java and .NET), HTTP Clients (ActiveX,
  Jscript, and Java), and Administration Tools.
• Windows (2000/XP) based with support for 64-bit
  and selected Unix operating systems announced.
  Also Webserverless access via the Tamino API for
  Java and a version for CD/DVD distribution.

31
4.1 Concepts

• Tamino XML Server is
• The XML Engine and Data Map (all the information
  for storing, indexing and processing XML
  objects).
• Full-text retrieval and two query languages
• X-Query (Tamino with W3C XPath) and XQuery (W3C).
• X-Node (view legacy databases in XML format and
  integrate external data sources).
• X-Tension (an XML-enabled interface to legacy
  processes and integrate existing applications).
• X-Application (finished components for Java
  Server Page applications).
• X-Plorer (Java interface with look and feel of
  Microsoft File Explorer).
• Support for the complete WebDAV standard and
  seamless integration with clients like Microsoft
  Office 2000 and 2003 (see Section 4.4.1).

Collaboratively edit and manage files on remote
Web servers.
32
4.1 Concepts

• Advantages of Native XML Storage and Tamino
  Server
• Relatively easy implementation of a low-cost data
  integration strategy based on XML.
• Protection of investments in core IT systems that
  need to be exposed to the outside as XML.
• Integrate existing systems at both the data level
  and at the application level (used in conjunction
  with EntireX).
• Helps reduce the cost of ownership of integrated
  electronic business applications by eliminating
  the need to map XML structures to relational or
  other structures.
• A staging platform that can offer significant
  performance and scalability advantages over other
  data storage and management strategies.
• Can act as both a directory and repository of Web
  Services with UDDI.
• Building XML Web Services on an XML virtual
  database view is easier, more portable, and
  cheaper than doing this with ordinary programming.

33
4.1 Concepts

• Advanced
• Most of todays information systems are based on
  relational techniques because relational database
  management systems dominate the enterprise IT
  culture.
• This is going to change because the closed
  Enterprise Information Model is giving way to a
  service oriented Open Network Information Model
  and because with XML it has now become possible
  to implement highly complex content in an open,
  natural, and straightforward way content that
  is becoming too complex for relational
  technology.

34
4.1 Concepts

• Advanced (continued)
• Developing complex information systems based on
  XML is a relatively young discipline and consists
  of the following basic steps
• (1) Conceptual model to XML Schema
• Model complex documents into a collection of
  interrelated document types.
• Notes The main purpose is to improve
  communication between the parties involved in the
  development process. Reverse engineering of
  relational schemata, under normal circumstances,
  leads to poor XML representation of the
  conceptual model because too much structural
  information is lost in the process. The Entity
  Relationship Diagram is not really well suited
  for the new open environment where XML is
  dominant.

35
4.1 Concepts

• Advanced (continued)
• Developing complex information systems based on
  XML is a relatively young discipline and consists
  of the following basic steps (continued)
• (2) XML Schema to Tamino
• Implementing XML Schemas in Tamino with
  strategies for namespaces, indexing, queries,
  transactions, and performance.
• Note XMI (XML Metadata Exchange) from UML tools
  can be converted into XML Schema with XSLT.
• (3) Utilizing Tamino Server Extensions
• Extend the built-in functionality of Tamino.
• (4) Rapid Application Development
• Implement a presentation layer with XSLT that
  derives HTML Web pages from presentation-neutral
  XML content.

36
4.2 Getting Started

• 4.2.1 Three Basic Tools
• 4.2.2 Three Basic XML Objects
• 4.2.3 Three Basic Steps
• 4.2.4 Animated Online Tutorials

37
4.2.1 Three Basic Tools

• The Tamino Manager
• Browser-based tool for administration of Tamino
  databases.
• The Tamino Interactive Interface
• A user interface to send request to the Tamino
  Server to load and retrieve XML objects or parts
  of them.
• The Tamino Schema Editor
• Allows one to define the schema as a graphical
  tree and automatically create the schema
  definition in Taminos schema language.
• Note Taminos schema definition language is
  based on the W3C XML Schema Standard with
  Tamino-specific information written in
  annotations to the XML Schema constructs.

38
4.2.1 Three Basic Tools
39
4.2.2 Three Basic XML Objects

• Doctype
• A root element of a DTD (Document Type Defintion)
  or XML Schema that denotes the documents start
  and ending point. In Tamino, it also represents a
  container for instances.
• Collection
• A Tamino-specific term which is the largest unit
  of information within a database. Each collection
  can contain multiple doctypes.
• Schema
• Tamino schema based on the W3C XML Schema
  standard with Tamino-specific information defined
  in annotations.
• Note Tamino distinguishes between a physical
  (how the XML documents are stored and indexed)
  and logical schema (the rules describing the
  relationship between and properties of elements
  and attributes in valid XML documents).

40
4.2.3 Three Basic Steps

• Steps (see next slide for Animated Online
  Tutorials)
• (1) Create a Tamino database and start it.
• (2) Load objects into the database.
• May requires defining a collection and schema.
• (3) Retrieve your loaded objects by querying the
  database.
• Note To write applications, recall from Section
  4.1
• Conceptual model to XML Schema.
• XML Schema to Tamino.
• Utilizing Tamino Server Extensions.
• Rapid Application Development.

41
4.2.4 Animated Online Tutorials

• The Animated Online Tutorials are short yet
  comprehensive animations which will help you to
  understand a particular feature in a minimum of
  time. The navigation buttons on the right of the
  animation's display can be used to stop, step
  backwards or forwards, or return to the
  beginning
• Creating, Starting and Stopping Tamino Databases.
• Creating and Defining a Tamino Schema.
• Browsing Through Tamino Databases.
• Specifying Queries to Retrieve Specific
  Instances.
• Tamino XQuery Tool - Specifying Queries to
  Retrieve Specific XML Data.

42
4.3 Training and Certification

• Software AGs XML Academy
• XML Engineer Certification
• At least 60 on 40 questions that must be
  completed in 120 minutes.
• Recommended Instructor-led Courses
• XML Introduction (2 days)
• Presentation of XML Documents Using Style Sheets
  (2 days)
• XML Application Programming with DOM and SAX (1
  day)
• XML Schema Development (2 days)

43
4.3 Training and Certification

• Software AGs XML Academy (continued)
• Tamino XML Engineer Certification
• Successful Completion of the XML Certification
  Test.
• At least 60 on 44 questions that must be
  completed in 120 minutes.
• Recommended Instructor-led Courses
• Tamino Usage and Administration (5 days)
• Tamino DOM API for ActiveX Programming (2 days)
• Tamino DOM API for Java Programming (2 days)

April 23-25, 2003 Tamino Tools for Application
Development (Short Course).
44
4.4 Online Resources

• 4.4.1 Demo Zone http//tamino.demozone.softwareag
  .com/mainSiteX/
• 1st Steps
• The "Tamino Real Estate Demo" quickly introduces
  you into the features of Software AG's XML server
  Tamino.
• XSLT
• The "Tamino XSLT Demo" demonstrates the
  advantages of XML stylesheet transformation
  (XSLT).
• XML Query
• The "Tamino XQuery Demo" lets you query XML
  documents stored in Tamino using W3C XML Query.
• Web Services
• The "Tamino Web Services UDDI Demo"
  demonstrates Tamino's capabilities as a
  UDDI-registry and features the exchange of SOAP
  messages in a Web Services scenario.
• WebDAV Server
• The "Tamino WebDAV Server Demo" explains the
  functionality of the Tamino WebDAV Server.

45
4.4.1 Demo Zone
1st Steps
46
4.4.1 Demo Zone
XSLT
47
4.4.1 Demo Zone
XML Query
48
4.4.1 Demo Zone
Web Services
49
4.4.1 Demo Zone
How UDDI Works
3) UDDI assigns a programmatically unique
identifier (UUID) to each tModel and business
registration and stores them in an Internet
registry
50
4.4.1 Demo Zone
WebDAV Server
51
4.4 Online Resources

• 4.4.2 Tamino XML Server Version 4.1.1 CD-ROM
• Tamino 4.1.1 Documentation
• Tamino XML Server
• Tamino API for Java
• Tamino API for .NET
• HTTP Client API for ActiveX
• HTTP Client API for JScript
• HTTP Client API for Java
• Tamino Schema Editor
• Tamino X-Plorer

52
4.4 Online Resources
4.4.2 Tamino XML Server Version 4.1.1 CD-ROM
53
4.4 Online Resources
4.4.3 Developer Community http//developer.softwa
reag.com/tamino/default.htm
54
5. Contact Information

• EPA
• Computer Scientist and XML and Web Services
  Specialist
• Office of Environmental Information (MC 2822T)
• U.S. Environmental Protection Agency (EPA)
• 202-566-1657
• niemann.brand_at_epa.gov
• http//www.sdi.gov
• Chair, CIO Councils XML Web Services Working
  Group
• bniemann_at_cox.net
• http//listserv.gsa.gov/archives/cioc-web-services
  .html
• http//web-services.gov