RE: [soa-rm-ra] words from today's telecon

["Chiusano Joseph" <chiusano_joseph@bah.com>]

In case it may help us regarding ebXML Registry vs. UDDI, here are 2 articles that I authored on the subject back in 2003:

 

“UDDI and ebXML Registry: A Co-Existence Paradigm” – WebServices.org, April 2003:

http://www.webservices.org/categories/technology/standards/uddi_and_ebxml_registry_a_co_existence_paradigm/(go)/Articles

 

“UDDI and ebXML Registry: A Three-Tier Vision” – ebXML Forum, August 2003:

http://www.ebxmlforum.org/articles/ebFor_20030824.html

 

Joe

 

Joseph Chiusano

Associate

Booz Allen Hamilton

 

700 13th St. NW, Suite 1100

Washington, DC 20005

O: 202-508-6514 

C: 202-251-0731

Visit us online@ http://www.boozallen.com

 

---

From: Ken Laskey [mailto:klaskey@mitre.org]
Sent: Wednesday, June 21, 2006 4:58 PM
To: Danny Thornton
Cc: soa-rm-ra@lists.oasis-open.org
Subject: [soa-rm-ra] words from today's telecon

Danny,

Following up on today's actions.  Words I had scribbled down were on service visibility:

Achieving SOA visibility requires 

- description creation and maintenance, 

- putting description in place where others can become aware of it,

- mechanism to establish awareness of description (e.g. registry, known cataloguing Web page, vendor I get all my services from, ...)

- mechanism to establish willingness of participants and availability of described service.

Also,  something I wrote for another purpose to decipher the registry/repository difference

1.1      A Registry or a Repository?

While the terms are often used interchangeably, the difference is important when looking at the functions provided by UDDI and ebXML.  Unfortunately, the formal definitions are less than clear. As described in the ebXML Registry Information Model specification [5], an ebXML Registry comprises both a registry and a repository where:

• The repository is capable of storing any type of electronic content such as XML documents, text documents, images, sound and video.  Instances of such content are referred to as repository items.
• The registry is capable of storing instances of metadata that MAY be used to describe repository items.  Instances of such metadata are referred to as registry objects.  Note, MAY is used in the sense of RFC 2119 [6] where by definition the subject of the MAY is neither formally required nor recommended.

To illustrate these concepts consider this familiar metaphor:

• An ebXML Registry is like your local library.
• The repository is like the bookshelves in the library.
• The repository items in the repository are like books on the bookshelves. The repository items can contain any type of electronic content just like the books in the bookshelves can contain any type of information.
• The registry is like the card catalog. It is organized for finding things quickly.
• A Registry Object is like a card in the card catalog. All Registry Objects conform to a standard just like the cards in the card catalog conform to a standard.
• Every repository item must have a Registry Object that describes it, just like every book must have a card in the card catalog.

To summarize, ebXML Registry stores any type of content as Repository Items in a repository and stores standardized metadata describing the content as Registry Objects in a registry.

In contrast, UDDI [7] comprises a set of services supporting the description and discovery of (1) businesses, organizations, and other Web services providers, (2) the Web services they make available, and (3) the technical interfaces which may be used to access those services. UDDI provides a registry in the ebXML sense but does not specify the mechanisms by which content identified and catalogued by the UDDI registry are stored.

------------------------------------------------------------------------------------------

Ken Laskey

MITRE Corporation, M/S H305     phone:  703-983-7934

7515 Colshire Drive                        fax:        703-983-1379

McLean VA 22102-7508