practical ebxml registry uses for interoperable ebusiness open forum 2003 on metadata registries...

Practical ebXML Registry uses for interoperable eBusiness

Open Forum 2003 on Metadata Registries

8:40am to 10am January 22, 2003

2Open Forum 2003 on Metadata Registries

Presenter

David Webber co-author of ‘ebXML – the new global standard

for doing business via the internet’, New Riders Publishing

Chair of the OASIS CAM TC Co-chair of OASIS/CEFACT ebXML JMT Pioneering XML eBusiness

[email protected]://drrw.net


Agenda

Part 1 – XML integration W3C approach – web-centric ebXML approach -

Registry-centric / assembly / core components

Upcoming Registry developments ebXML V3.0 enhancements Partner discovery / UDDI

Part 2 – Demonstration / Technologies Review of OAGIS V8.0 technology ebXML Registry and Content Classification Summary / Q&A


ebXML Registry

Part 1


1990 1995 2000 2005 2010

RPC / WebServices

ebXML

WebeCommerce

EDI

Electronic Business Technologies


ebXML Adoption

NorthAmerica

Europe Asia

Government

Commercial

Industries

Q4 - 2002


CCSDCEFACT

BPSSCEFACT

UMM/UML

XML

UN/EDIFACT

UBL

OAG BODs

ContentAssembly

Standards Chemistry M

arke

t Ado

ptio

n

Open Standardization

Proprietary JCV Consortia SDO

SGMLISO

XMLW3C

SOAP v1.1 SOAP v1.2W3C

UDDI v3UDDI.org

WSDL v1.2W3C

eb MS v2OASIS

WSDL v1.1

UDDI v3xOASIS

eb Reg v2OASIS

Traction

Standing

ebXML spec’s

web services


W3C approach

Web-centric


The need for XML

XML – eXtensible Markup Language.

XML makes data portable.

XML is a global standard with pervasive use.

XML can be built from any structured data

(DB’s, EDI, TEXT).


<?xml version=“1.0”?><Data> <Item ID=“112”> <Name>Rod</Name> <Price>12.00</Price> <Units>1</Units> </Item> <Item ID=“114”> <Name>Reel</Name> <Price>15.00</Price> <Units>1</Units> </Item> <Item ID=“120”> <Name>Bait</Name> <Price>24.00</Price> <Units>3</Units> </Item> </Data>

XML is self-annotating


<lat_deg>30N</lat_deg>

<latitude units=“degrees” hemisphere=“north”>30</latitude>

<latitude> <hemisphere>N</hemisphere> <degrees>30</degrees></latitude>

These 3 XML fragments are:• Equally valid ways to express the same data in XML• Well-formed per W3C Specification• Different terms and syntax

NOT INTEROPERABLE!

XML Management Challenges


No Single Standard can be imposed! Various industry communities will adopt

multiple “standards:” Government (message, database, symbology),

Commercial, International, de facto/legacy etc.

Expect Heterogeneity!

Lessons Learned


W3C Schema Provides

Definition of all permitted element structural combinations

Ability to define local typing constraints Ability to create re-usable chunks of structure

elements


W3C Schema weaknesses

Permitted combinations of attributes within elements

Content assembled from multiple namespaces and cross-associations

Context mechanism has to be externally resolved using XSLT

All semantics are in the schema


ebXML Approach registry-centric assembly and context core components legacy non-XML payloads


“Who, What, When, How”

Trading Profile Management and Discovery.

Assembly of transaction content.

Establishing consistent data definitions

Business Process Collaboration.

Message Handling Services

Web Services

What does ebXML do?


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


BusinessAnalyst

Registry User Interface

InformationProfiles

andTransform

MappingTemplates

Content/ Rules

Access

Program LevelSemantics

Registry Search Toolsand Information Engine

Industry Business StandardsRegistry Protocol StandardsebXML, ISO11179, OASIS,

UDDI, xCBL, RosettaNet, Biztalk

XML/EDI

Software Developers / Tools

Interchange

Registry Interactions :


ebXML Registry capabilities

Provides services for sharing information Provides publishing and discovery of information Accessible as a web service Communicates using XML based request and

responses Provides mechanisms to store and retrieve

persistent information Includes a Repository


XML, by itself, does not solve interoperability problems yet it is an important tool for doing so.

XML does not provide semantics. XML by itself is not the magic bullet. What we really need is a consistent set of

methods for building interoperable eBusiness systems using XML – “railroads and telephony”.

XML itself is not enough


XMLbusiness information

Schema

Delivery Assembly

Schema: Content structure definitionandsimple content typing

Content Assembly: Business logic forcontent structure decisions andexplicit rules to enforce content,and interdependencies, with business exchange context, and content definition UID references

ebXML Secure Authenticated Delivery and Tracking: ebXML Messaging system, envelope format and payload with exchange source profile (CPP) controls

UID content referencing systemensures consistent definition usage

UID

Registry/Dictionary

(and long-term consistency)

XML Information Exchange Quality


<ListPrice>9.99</ListPrice>

XML Instance XML Instance

<UnitPrice>9.99</UnitPrice><Currency>$</Currency>

CollaborationPartner #1


Data

Machine-to-Machine

Business

Consistent Meaning


Context Everywhere!

Registry

OAG304

ListPrice Currency

DollarsUnitPriceCollaborationPartner #1

<Rep href= “http://www.oag.org”>OAG</Rep>

<ELEMENT rep= ‘OAG’ name=‘ListPrice’ uid =‘OAG304 >


<ELEMENT rep= ‘OAG’ name=‘ListPrice’ uid =‘OAG304 >

Schema or Template


<ELEMENT rep= ‘OAG’ name=‘UnitPrice uid =‘OAG304 >


<ELEMENT rep= ‘OAG’ name=‘UnitPrice uid =‘OAG304 >

Schema or Template

UIDs allow for domain crosswalks and light transactions


<ListPrice>9.99</ListPrice>

XML Instance XML Instance

<UnitPrice>9.99</UnitPrice><Currency>$</Currency>

Data


Classification Structure

Taxonomiese.g. Dewey Decimal

Industry

HealthCare Automotive Retail

Geography

USA Japan Europe

Ford:object

Chevy:object

Toyota:object

Nissan:objectBMW:object


Information Methodologies

Final BusinessPayload

Payload Metadata

PayloadMetadata

UN/CEFACT Core Components

Information Components

UMM / UMLModeling

LegacyData

TOPDOWNAPPROACH

BOTTOMUPAPPROACH


Registry-centric benefits

Legacy payloads can be used “as is” Supports vocabulary alignment and multi-

lingual element tags Minimizes overhead in payload itself – can be

just simple structure Provides ability to do automated mapping Uses Content Assembly Mechanism to

capture business rules and context parameters (OASIS CAM TC)


Business Process Pyramid

Technology Integration

Business Integration

VerbsVerbs

Motivation Time People

MessagesMessages

RulesRules EventsEvents

ProcessProcess

RolesRoles

Specifications Schema

Workflow

Contract

Secure contentdelivery

Secure contentdelivery

Directory Services

Collaboration PartnerProfiles


2

1

3

4

5

Presentation

Collaboration PartnerAgreements


Artifact relationships

AssembliesAssemblies

BP SpecificationBP Specification

NounsNouns

Data/Codes Services/Functions Network

XFormsXForms

ebMS/SOAPebMS/SOAP

Registry Taxonomy

Web ServicesWeb Services




MessagesMessages



RulesRules

EventsEventsRolesRoles

2

35

VerbsVerbsNounsNouns

Secure ContentDelivery

Secure ContentDelivery

MessagesMessages

VerbsVerbs

NounsNouns

5

6

To/From

Partner

eBusiness delivery flow

Payload

Registry

Messaging

BP engine

ContextContext

ContentAssemblyTemplates

ContentAssemblyTemplates

ProcessProcess

AssemblyAssembly

Business Process Catalogue

Business Process Catalogue

1

BusinessApplication

ContentAdaptors

Mapping

Templates

4


ContextValuesContextValues

RequiredContent

Structure

RequiredContent

Structure

ProcessEngine

ProcessEngine Content

ReferencesContent

References

1

Payload / RenderingPayload / Rendering

2

Content Assembly MechanismTemplate

Content Assembly MechanismTemplate

Payload MappingPayload Mapping

3

ApplicationDatabase

ApplicationDatabase

RegistryComponents

RegistryComponents Conceptual

Logical

Physical

Concept to Runtime Approach

Vocabulariesand

Industry Dictionaries

Vocabulariesand

Industry Dictionaries

Business Re-usable Information

Components- BRICs

Business Re-usable Information

Components- BRICs

StructureChoices

StructureChoices


Assembly components


Registry Lookup


CPP/A

eBusiness Runtime Components

O/S

App Server

ebXML MS URL configPort

Security

BPEE

BP Rules

BPSS

I/O

Payload(s)

ebXMLMessageContent

Registry Server


O/S

App Server

ebXML MS

BPEE

BP Rules

CPP/A

I/O

BPSS

APITRANSFORMS

Instancevalues

TransformTemplates

Assembly Templates

Backend Integration


Part 2

Upcoming Features,

Implementing ebXML, and

Registry Demonstration


Upcoming Registry Developments

V3.0 ebXML, UDDI, ISO11179


New Features in Version 3.0

Cooperating registries Event notification HTTP interface to registry Content management services Iterative query support


Cooperating Registries

Enables multiple ebXML Registries to work together to address user needs

Based on a loosely-coupled federation model Allows local autonomy to each registry operator Enables smaller registries to access resources of

larger registries Enables federated queries to multiple registries

Inter-registry object references A registry may belong to multiple Federations


Event Notification

Enables notification of events regarding registry objects

Clients may be registry users or other registries Leverages existing Registry Services interfaces Subscription Service registers clients for

notification Supports e-mail notification and programmatic Flexible notification options

References to event Actual event Objects affected by the event


HTTP Interface to Registry

Provides a pure HTTP interface to Registry Does not require SOAP Registry objects and Repository items

addressable via URLs

Allows ebXML Registries to interoperate with other types of registries

Improves access to Registry content


Content Management Services

Enables content management based on object type

Content cataloging and validation Validate on submission Cataloging metadata applied on submission

Content-based publish, discovery and subscribe

User-defined relationships between content Associations of internal and external

classification Invocation control file defines rules for

cataloging service


Cataloging Invocation Model

Content Management

Service

2. SubmitObjectRequest

ebXML RegistryRegistry Client

3. Content

Management

Service

Request

4. Content

Management

Service

Response

Content +Metadata

Content +Metadata

InvocationControl

File

6. RegistryResponse

5. commit

1. SubmitObjectRequest Service

PersistentStore


Deploying ebXML Technologies

Planning and Implementation Guide


Deployment Planning

Incremental adoption of components and operational maturity

Plan 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. Web services and discovery.


Implementing ebXML roadmap

Existing Integration New Deployment

1 Install messaging Install messaging

2 Create partner delivery details Create partner delivery details

3 Document business process Agree on business process

4 Migrate existing payloads to new delivery

Make assembly definitions

Select payload standards

Make assembly definitions

Map to applications

Build payload content

4 Adopt Business Process automation - BPSS

Adopt Business Process automation - BPSS

5 Cross reference assembly to registry dictionary

Cross reference assembly to registry dictionary

6 Publish details to registry Publish details to registry

I N C

R E

A S

I N G

M A

T U

R I T

Y


Some ebXML selection metrics

• B2B or large A2A Environments— extending or integrating enterprise systems, or when loosely coupled messaging is desirable

• Need Reliable Messaging— when enterprise services perform updates, insert, or deletes to the underlying data model, reliable messaging becomes critical

• Security is a Concern—when different security profiles and requirements exist between trading partners

• High scalability requirements—ebXML’s loosely coupled messaging architecture allows for horizontal scalability, queuing, and clustering

• Want to Leverage Industry Standards—XML grammars, business process modelling and trading partner agreements


Main ebXML concepts

Business Processes – defined as models in UMM, scripted in XML

Business Messages – content agnostic - exchanged using ebMS

Trading Partner Agreement – specifies parameters for businesses to interface with each other – expressed in XML

Messaging Layer – moves the actual XML data between trading partners – ebMS

Core components – library of pre-defined business vocabulary artifacts

Collaboration Registry - Provides a “container” for process models, vocabularies, assembly templates, partner profiles + discovery.


Additional Information

OASIS ebXML Registry Technical Committee http://oasis-open.org/committees/regrep/

OASIS CAM (assembly) Technical Committee http://oasis-open.org/committees/cam/

ebXML.org http://www.ebxml.org/

Version 2.0 Implementations Open Source Implementation

http://sourceforge.net/projects/ebxmlrr ebxmlsoft Inc. Implementation

http://www.ebxmlsoft.com/ XMLGlobal Implementation

http://www.xmlglobal.com/


http://www.ebXML.orghttp://drrw.net

Thank Thank youyou

Pioneering XML eBusinessPioneering XML eBusiness

practical ebxml registry uses for interoperable ebusiness open forum 2003 on metadata registries...

Documents