# Presentation: 248947

## Deploying
Registry Systems

August 2001

**Registry Systems**
**August 2001**

- XML Gov – August 2001.

## Presented by

- David RR Webber
- XMLGlobal Technologies
- co-author of ‘ebXML - the new global standard for doing business on the internet’,
- New Riders Publishing.

## Agenda

- Introduction
- Quick Review of ebXML Technical Architecture
- Business Value of Registry in ebXML
- Business System integration needs
- Concepts of crosswalks and core components
- Brief note on SOAP base interchanges
- NIST Registry Prototype
- DISA DRIve for migration of legacy X12/EDI
- Broader Registry Models and Roles
- Registry Implementation Planning

## Introduction

- Review of Registry landscape

## ebXML Technical Architecture

## 	ebXML enables anyone, anywhere to do business with anyone else over the Internet

**ebXML Mission**

**Notes:**
What does ebXML do? The short answer is ebXML enables anyone, anywhere to do business with anyone else over the Internet.

## What ebXML does

- Trading Profile Management and Discovery.
- Business Process Collaboration.
- Exchange of XML business semantic knowledge.
- Assembly of transaction content.

## Automating Trading Partner Setup

**Automating Trading Partner Setup**

**ebXML Server**

**ERP PO**

**XML PO**

**OASIS XML.org **
**Repository**

**ebXML Service**
**Layer**

**Custom LOB**

**Custom Invoice**

**ERP**
**System**

**Accounting **
**System**

**ebXML Server**

- Exchange Profiles to
- quickly configure relationship

## Enabling Business Processes

- Classification structures
- Registration of business domains
- Detailing of process steps
- Facilitation and Choreography details
- Linkage to Core Components

## Vision – Business Value of Registry

*“**A semantic registry is the key foundation block upon which global electronic business exchanges will be built”.*

## Mission

**Collaboration** - give industry groups and enterprises the ability to share business semantic information and business process interfaces.
**Semantics** - provide universal infrastructure that seamlessly delivers semantic integration into business applications.
**Interfaces** - open deployment machine-to-machine and user web enabled visual.

## eBusiness Registry Legal Role

- Service that manages and secures business interaction information in a consistent way that is compliant with emerging international standards and technical specifications.

## Registry Audience

**Business Analysts** – manage business process definitions and partner interchange profiles; classify content by industry domain.
**Business Users** – can find what they need to initiate business processes using simple menus and choices.
**Programmers** – can publish formal software definitions of process components.

## Business Integration Needs

- Crosswalks and Core Components

## Build Upon Existing Infrastructure

**Business Broker**

**Registry**

_**Hub n’ Spoke**_

_**I**__**nformation **__**S**__**ervices **__**L**__**ayer**_

**Centralized data processing only, Weak Metadata Strategy, **
**Virtual Pt.-to-Pt.**
***Technology Solution***

**Central &Distributed data processing, **
**Enterprise Metadata Strategy, **
**Pt.-to-Pt. Mechanisms via Queuing**
***Business Solution***

- Allowing for both central and distributed computing

**Data**

**Data**

**Metadata**

## XML driven service layer(s)

**XML driven service layer(s)**

- Content

- Data

- Services

- XML

- XML

- XML

- XML

- XML

- XML

- XML

- XML

- XML

- Business
- Enterprise

- Information Services Layer

- Open Socket Interface

- Business Systems

- Process Integration

- Customers

- Systems Integration

- Partners

## Goal: Single face Solution

**Trading Partners**

**Single Interface**

**Corporation**

**Goal: Single face Solution**

- Integration at point of use.

**Need to derive **
**core components **
**and standard**
**business**
**processes**
**to reduce **
**interface **
**complexity**

## Using Bizcodes to identify content

- EAN Barcode links physical product to an abstract entity

- Electronic Representation

- Of Abstract Entity:  (catalogue)

- Catalogue entry:
- <Part>
- <Name>
- <Price>
- <ARO>
- <Make>
- <Weight>
- <Units>

- Bizcode

- Bizcode

- Bizcode

- Bizcode

- Bizcode

- Bizcode

- Bizcode

- Bizcode

- Bizcode links physical attributes to properties of entities.  Entities can be physical or abstract.

- ebXML UID = Bizcode

## Context Everywhere! BizCodes = UIDs

**Context Everywhere!**** *****BizCodes = UIDs***

**<****ListPrice****>9.99</****ListPrice****>**

**DCR****epository**

**VI304**

**ListPrice**

**Currency**

**Dollars**

**XML Instance**

**UnitPrice**

**XML Instance**

**<****UnitPrice****>9.99</****UnitPrice****>**

**Collaboration**
_**Partner #1**_

**X12**

**EDIFACT**

**<Rep href****= ****“****http://www.disa.mil****”>****DISA****</Rep> **
**<****ELEMENT**** ****rep= ‘****DISA****’**** ****name****=‘****ListPrice’**** **** ****Biz =‘****VI304****’**** >**

**Schema *****or Template***

**<Rep href****= ****“****http://www.disa.mil****”>****DISA****</Rep> **
**<****ELEMENT**** ****rep= ‘****DISA****’**** ****name****=‘****UnitPrice’**** **** ****Biz =‘****VI304****’**** >**

**Schema *****or Template***

*BizCodes allow for domain crosswalks and light transactions*

**Collaboration**
_**Partner #2**_

## Relationship of and use of UID 

- Content within the Registry must give access to discovery down to the attribute level via a consistent methodology. In order to enable this functionality, the use of *Unique Identifiers* (*UIDs*) is required for all items = Bizcodes
- These *UID* references are implemented as *XML* attributes, expressed as fixed value attributes for each of the physical *XML* elements and structures.

## Core Component Model

## NIST Interoperability Prototype 

- Demonstration

## Concept Architecture

- Server

- XML Global Registry

- Browser
- Client

- HTML DOM

- XML Content

**ebXML **
**syntax**

**SOAP **
**syntax**

**JavaScript**

- Server

- NIST OASIS Registry

## NIST Concept - online access

- Business context – CatXML
- (_[http://www.catxml.org](http://www.catxml.org/)_)
- Catalogue information integration model:
- _[http://nist.xmlglobal.com](http://nist.xmlglobal.com/)_
- _[DEMO](file:///../../windows/TEMP/NIST-prototype.htm)_
- nist2001 / xmlgnist

## DRIve - bridge for legacy systems

**Registry**

- Core

- Components

- Templates

**ebXML**

** ****Compliant**

**Query/Response Interface**

**Element Definitions**

**Transformation Services**

**Control Templates**

**Transformation Service Layer**

**Content Domains**

**DISA**

**X12**

**EDI**

**OAG**

**BOD's**

**XBRL**

**Accounting**

**Filters**

- Core

- Components

**Element Definitions**

- Core

- Components

**Element Definitions**

**Transaction Assembly**

**Transaction Assembly**

**Transaction Assembly**

## Registry Models

- Mission separation for registries – ISO11179, ebXML, OASIS, UDDI.

## Mission Separation

- ISO11179 – heritage is from EDI world, centered  on data dictionary synchronization and metadata registry harmonization across large enterprises.  Extensive librarian, versioning and tracking controls.
- OASIS – heritage from SGML document-centric world.  Focus is on mixed content information model.
- ebXML Registry – A2A focus for eBusiness automation.
- UDDI – business directory services and automated trading partner discovery – overlap with ebXML secondary role.

## ebXML integration approach

**ebXML integration approach**

- ISO11179
- Registry

- ebXML
- Registry

**ebXML interface service**

**ebXML transport layer**

- Semantic
- content store

- XML semantic
- content

- PUSH

**Extractor**

**XML interface service**

**Marked content domain for extraction**
**Classification synchronization**

**Classifications**
**Associations**

**Classifications**
**Associations**

## Gap Analysis

- Subscription Registries – Microsoft BiztalkTM registry and OASIS XML.org provide only limited librarian authority and controls. No API.
- Local registry – provides your own domain, services and presence, that links into and extends what the central registries offer.
- Plus – partner profile management and XML A2A machine interfaces give direct support for dynamically driven eBusiness applications.

## Registry Layers

**UML**
**Tools**

**XML Content**

**Metadata Information Registry/Repository**

**Web User Interface**
**Program API Support**

- Business Transaction Generators
- Dictionary Content
- Transformation Services
- Scripting

- Domains
- Content Discovery
- Topics and Packages
- Dynamic Process Component Enabling

-  Industry Dictionary
-  Business Processes
-  Business Transactions
-  Business Forms

- HTML forms
- XML Calls

- Modelling and Workflow Integration

- Information Store

- Tools and services

- High level modelling systems integration
- Business Process Definitions
- Workflow Control
- Interchange Profiles

**Communications Layer**

## Summary

- Need
- Provide semantic registry
- Human interface
- Machine interface
- Issues
- Classification and Associations
- UID and content notation synchronization
- Registry of Registries (UDDI one option)
- Certification of Registry implementations

## Planning

- 1 year, 2 year and 5 years out.
- Issues, implementation criteria, ROI, support, interoperability, XML.
- Schema neutral content assembly.
- Separation of business semantics from XML mechanics.

## Assumptions for Success

**Not much different than any other new technology infusion...**
** ****Top management buy-in**
** ****Provide guidance to architects and lead developers**
** ****Metrics; collection and evaluation **
** ****Best of breed tools for developers and end-users**
** ****Establish a resourced plan and execute**

## Thank you

- _[david.webber@XMLglobal.com](mailto:david.webber@XMLglobal.com)_

***Thank you***

**The XML Global AdvantageTM**