# Presentation: 035245

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

- Joel Patterson
- Software AG
- July 23, 2003

## 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 (ITRACT)
- 8. Web Services Network Provider

## 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/registries.asp

## 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)

## Delivering Information on Demand

-  Enterprise Metadata Registry/Repository

**Delivering Information on Demand**

## 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.)

**Benefits of the EMR**

## Discussion Points

## 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

## 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](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_id=43](http://it.ojp.gov/topic.jsp?topic_id=43)_
- _[http://it.](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[ojp](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[.](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[gov](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[/](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[jxdd](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[/](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[JusticeXMLTechnical](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[.](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)__[pdf](http://it.ojp.gov/jxdd/JusticeXMLTechnical.pdf)_
- 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](http://justicexml.gtri.gatech.edu/technical/intro/wrapped-index.html)_

## 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 Chiusano’s Core Components and ebXML Registry presentation)

## 4. Web Services and UDDI

**UDDI Registry**

**White Pages**

-  Business Name
-  Contact Information
-  Description

**Yellow Pages**

-  Services and Products
-  Industry Codes
-  Geographic Index

**Green Pages**

-  Ebusiness Rules
-  Service Descriptions
-  WSDL

- Figure 4.6 A UDDI Registry as a conceptual phone book.

- 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.

## 4. Web Services and UDDI

- Demo Zone: http://tamino.demozone.softwareag.com/mainSiteX/

- 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.

## 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

## 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/mainSiteX

## 7. Semantic Web

- RDF: Application Integration Hub

## 7. Semantic Web

- These triplets form complete statements.

-   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.

**Subject**

**Predicate (property)**

**Object**

**Resource Description Framework (RDF)**

## 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.

## Intelligence Tracking and Relationship Analysis for Counter Terrorism (ITRACT)

- Intelligence Analysis Methodology
- and Process Description

**Steven C. Davis**
**Dr. Barry M. Horowitz**

**Intelligence Tracking and Relationship Analysis for Counter Terrorism (ITRACT)**

## 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.

## 8. Web Services Network Provider

- Web Services Network:
- Security
- Reliability
- QoS
- Billing

- Service providers

- Service requestors

- Web services networks act as intermediaries
- in Web services interactions.

## Questions?

- Contact Information:
- Joel Patterson
- Software AG
- _[joel.patterson@softwareagusa.com](mailto:joel.patterson@softwareagusa.com)_
- 703-391-8245