A Government Enterprise Component Registry and Repository Using Native XML Database Management Techn

1
A Government Enterprise Component Registry and
Repository Using Native XML Database Management
Technology

• Joel Patterson
• Software AG
• Brand Niemann, Chair,
• XML Web Services Working Group
• July 22, 2003

2
Outline

• Registries and Repositories
• Software AG
• Tamino XML Server
• Enterprise Metadata Repository (EMR)
• Discussion Points
• 1. Top 6 Features Joe Chiusano
• 2. ISO 11179
• 3. ebXML
• 4. Web Services and UDDI
• 5. Native XML Database Management
• 6. Web Distributed Authoring and Versioning
• 7. Semantic Web
• 8. Web Services Network Provider

3
Overview

• The full benefits of XML will be achieved only if
  organizations use the same data element
  definitions and those definitions are available
  for partners to discover and retrieve.
• A registry/repository is a means to discover and
  retrieve documents, templates, and software
  (i.e., objects and resources) over the Internet.
• The registry is used to discover the object. It
  provides information about the object, including
  its location. A repository is where the object
  resides for retrieval by users.

Source XML Working Group, http//xml.gov/registri
es.asp
4
Why Software AG?

• Government data is being stored in XML format
• E-Gov
• GPEA
• Many registries rely on XML for storage of the
  information
• XML allows for metadata and maximal flexibility
• Tamino XML Server
• native XML database
• Highly scalable
• Stable, proven technology
• Enterprise Metadata Registry/Repository (EMR)

5
Delivering Information on Demand
Enterprise Metadata Registry/Repository
6
Benefits of the EMR

• Enable Enterprise Information Integration (EII)
• Create virtual views across multiple data sources
• Decrease development time
• Increase productivity
• Enterprise-wide accessibility
• Gain control of your distributed systems metadata
• Enhance control over systems in production
• Centralized management
• Develop dictionary of business nomenclature
• A key source of information for systems
  documentation
• Capture metadata using commonly accepted open
  standards
• CWM (Relational Models, OLAP, Business
  Intelligence, etc.)
• UDDI (Web Services)
• Legacy Integration (3270 Screen maps, XSLT
  transformations, etc.)

7
Discussion Points
8
1. Top 6 Features

• Joe Chiusano, January 16, 2003
• Namespace Management Function.
• Security.
• Distributed Federated Capabilities.
• Granularity.
• Classification/Taxonomy Support.
• ebXML Core Component Enablement
• Demonstration of Classification/Taxonomy via EMR

9
2. ISO 11179

• organizations use the same data element
  definitions
• EPA
• EPA ISO 11179 Data Standards
• Excel Spreadsheet (May 15, 2003).
• Interim XML Registry for the Environmental
  Information Exchange Network
• http//oaspub.epa.gov/emg/xmlsearch.startup
• Pilot to check conformance of XML Schemas to
  data standards.
• Global Justice
• Justice XML Data Model CD-ROM (May 23, 2003).
• http//it.ojp.gov/topic.jsp?topic_id43
• Census
• GIDS Use of ISO 11179 Metadata Registry to Design
  Forms and Import Wizard for Mapping Data Elements
  to One Another.
• Demonstration of Justice XML Model
• Import of 27 other schemas
• Georgia Tech Research Institute Justice XML
  Project
• http//justicexml.gtri.gatech.edu/technical/intro/
  wrapped-index.html

10
3. ebXML

• ebXML (Electronic Business using XML)
• To provide an open XML-based infrastructure
  enabling the global use of electronic business
  information in an interoperable, secure and
  consistent manner by all parties
• Suite of specifications
• Business Process Business Process Specification
  Schema
• Core Components common set of semantic building
  blocks
• Collaboration Protocol Collaboration-Protocol
  Profile and Agreement specification
• Messaging ebXML Messaging Service (ebMS)
• Registry/Repository information model and
  services for the registration, storage and
  maintenance of information
• (taken from Joseph Chiusanos Core Components and
  ebXML Registry presentation)

11
4. Web Services and UDDI
Pilot 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.
UDDI Registry
Yellow Pages
Green Pages
White Pages

• Services and Products
• Industry Codes
• Geographic Index

• Ebusiness Rules
• Service Descriptions
• WSDL

• Business Name
• Contact Information
• Description

Figure 4.6 A UDDI Registry as a conceptual phone
book.
12
4. Web Services and UDDI
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.
Demo Zone http//tamino.demozone.softwareag.com/m
ainSiteX/
13
5. Native XML Database Management

• This is what we do!
• (1) heterogeneity (the real world is not
  organized into tables, rows and columns-express
  information as it exists without restriction)
• (2) extensibility (new types of data can be added
  at will allowing one to embrace, rather than
  avoid, change) and
• (3) flexibility (data fields can vary in size and
  configuration from instance to instance - XML
  imposes no restriction on data).
• Demonstration from Justice XML Data Model

14
6. Web Distributed Authoring and Versioning
The "Tamino WebDAV Server Demo" explains the
functionality of the Tamino WebDAV Server.
Demo Zone http//tamino.demozone.softwareag.com/m
ainSiteX
15
7. Semantic Web
RDF Application Integration Hub
16
7. Semantic Web
Resource Description Framework (RDF)

• Object-oriented Semantic Web metadata language
  for linking
• information
• The foundation of RDF is sets of triplets, each
  consisting of a
• subject, predicate, and object.

Predicate (property)
Subject
Object
These triplets form complete statements.
17
7. Semantic Web

• Storage and Re-Use of RDF
• Scalability for triples (millions)
• E.g., XSD 1000s and RDF millions!
• Also lots of content in non-XML formats.
• Demonstrations
• ITRACT (Intelligence Tracking and Relationship
  Analysis for Counter Terrorism) and Non-Obvious
  Relationship Associations.

18
Intelligence Tracking and Relationship Analysis
for Counter Terrorism (ITRACT)
Intelligence Analysis Methodology and Process
Description
Steven C. Davis Dr. Barry M. Horowitz
19
Project Objective
To explore intelligence collection and analysis
solutions for counter terrorism that apply and
integrate leading-edge technologies to permit
non-obvious relationship discovery
20
Two Major System Components

• Hierarchical Holographic Modeling (HHM)
• UVA-developed technique to identify sources of
  risk and to develop scenario templates
• Resource Description Framework (RDF)
• W3C standard for a conceptual model to specify
  relationships between data items that is
  XML-based

21
Tracking and Preempting Scenarios of Terrorism

• Scenarios can be characterized as a set of
  potential attacks that can be commonly treated
• Food poisoning attacks
• Water poisoning attacks
• Nuclear power plant attacks
• In order to preempt a specific attack we want to
  use information on
• Target to be attacked
• The people engaged in preparing for the attack
• The method of attack
• We use this information to help us to discover
  non-obvious relationships that can reveal an
  attack under preparation

22
Demonstration Setup

23
8. Web Services Network Provider
Source Business Integration Driven by Business
Lines A perspective on the Data Reference Model
as it relates to Cross Agency Challenges.
Standards Based Architecture to Support Federated
Data Management, Industry Advisory Council (IAC)
Enterprise Architecture SIG, May 28, 2003.
24
8. Web Services Network Provider
Service requestors
Service providers
Web Services Network Security Reliability QoS Bil
ling
Web services networks act as intermediaries in
Web services interactions.
25
Questions?

• Contact Information
• Joel Patterson
• Software AG
• joel.patterson_at_softwareagusa.com
• 703-391-8245