Re: [regrep] UDDI FAQ entry on ebXML Registry - Rex Brooks - org.oasis-open.lists.regrep

20 messages in org.oasis-open.lists.regrepRe: [regrep] UDDI FAQ entry on ebXML ...

From	Sent On	Attachments
Carl Mattocks	Jan 14, 2004 6:50 am
Farrukh Najmi	Jan 14, 2004 6:56 am
Anne Thomas Manes	Jan 14, 2004 7:03 am
Luc Clément	Jan 14, 2004 7:07 am
Berry, Nicholas F	Jan 14, 2004 4:43 pm
Chiusano Joseph	Jan 14, 2004 10:37 pm
Anne Thomas Manes	Jan 15, 2004 4:24 pm
Anne Thomas Manes	Jan 15, 2004 4:24 pm
Luc Clément	Jan 15, 2004 10:14 pm
Rex Brooks	Jan 16, 2004 3:59 am
Chiusano Joseph	Jan 16, 2004 6:25 am
Duane Nickull	Jan 16, 2004 9:00 am
Breininger, Kathryn R	Jan 16, 2004 9:18 am
Rex Brooks	Jan 16, 2004 10:09 am
Chiusano Joseph	Jan 16, 2004 10:26 am
Rex Brooks	Jan 16, 2004 12:47 pm
Anne Thomas Manes	Jan 16, 2004 2:19 pm
Rex Brooks	Jan 16, 2004 2:41 pm
Farrukh Najmi	Jan 16, 2004 3:14 pm
Anne Thomas Manes	Jan 17, 2004 8:58 am

Subject:	Re: [regrep] UDDI FAQ entry on ebXML Registry
From:	Rex Brooks (re...@starbourne.com)
Date:	Jan 16, 2004 10:09:09 am
List:	org.oasis-open.lists.regrep

My comments inline also:

At 9:34 AM -0500 1/16/04, Chiusano Joseph wrote:

Please see comments inline [JMC].

Rex Brooks wrote:

Why not add a note to the effect the ebXML and UDDI are interoperable and can be used in a complementary fashion.

[JMC] What does "complementary" mean here?

Different focus, ebXML seems to be better at serving societal, governmental needs as well as broad spectrum business concerns, while UDDI allows a more narrow focus on business segments or vertical markets (per below), if a vertical market wants to have its own registries. Complementary efficiencies.

Healthcare is an apt example, especially wrt Emergency Management supply chains that also intersect or include governmental procurement needs.

You might want to coordinate these FAQ messages with the UDDI TC's FAQ and identify areas where both say ebXML and UDDI each are designed with a particular market segment in mind,

[JMC] I respectfully recommend we stay away from mentioning market segments for this purpose, especially because many folks have different views of a what a "market segment" means (I personally was thinking more of verticals such as health care, finance, etc.)

That's be fine with me.

[End of JMC comments]

Ciao--Rex

with ebXML specifically

serving Business and Government in a wider focus beyond Web Services, which explains why ebXML provides a registry and repository, while UDDI focuses more on the Business in general and Web Services in particular, and does not provide a repository in favor of allowing particular Business Segments to be served by more specialized repositories provided by Business interests? Both ebXML and and UDDI can each say that there specifications serve the complete spectrum, so that neither is perceived as being so limited that either Business or Government segments need to use both, but can choose to do so in order to take advantage of the more specialized interaction channels provided.

I, for one, would like to see the implicit competition dissolve and/or change into cooperation and coordination. FWIW, I recognize that the Business side has more adamant adherents who have actively pursued the ascendency of their more limited (read centralized and platform-specific) focus. In their defense, I think it is wise to recognize that it is also due to company-specific myopia, and a reluctance to accept the necessity of supporting a wider range of interests (more work) rather than monopolistic practices per se. That is also not to say that some unnamed parties are largely incapable of acting outside of their monopolistic default state unless prompted by market conditions or legal action.

Ciao, Rex

At 7:33 PM -0500 1/15/04, Anne Thomas Manes wrote:

How about this:

The ebXML Registry is a constituent of the Electronic Business using XML (ebXML) standard, which develops standards and protocols to support business-to-business (B2B) operations. The ebXML Registry TC has defined a registry specification, known as ebXML Reg/Rep, for publishing and discovering shareable content and metadata. The ebXML Reg/Rep is both a registry and a repository. Although designed to support the discovery requirements for ebXML, the ebXML Reg/Rep may be used as a general-purpose registry and repository.

The UDDI specification defines a registry service focused on supporting the requirements for publishing and discovering Web services. UDDI does not include a repository. Although designed to support the discovery requirements for Web services, UDDI may be used as a general-purpose registry.

At 11:14 AM 1/15/2004, Berry, Nicholas F wrote:

Most of my critique of Farrukh's FAQ statement is grammatical.

My comments/changes are in red. I would have used "strikeout" but my Outlook program has disabled it for some reason. Hence, I've included Farrukh's original beneath mine for reference. Thanks for putting up with a lurker's comments.

--Nicholas

<Nicholas> The ebXML Registry is a constituent of the Electronic Business using XML (ebXML) standard, which develops standards and protocols to support business-to-business (B2B) operations. The ebXML Registry TC has defined a general purpose registry specification*, known as ebXML Reg/Rep, for publishing and discovering shareable** content and metadata***. The ebXML Reg/Rep is both a registry and a repository.

UDDI, managed by the UDDI Spec TC, is focused as a registry service for Web services and its artifacts. [I don't believe it's wise for Reg/Rep to attempt a definition of UDDI in this particular space....leave that for the ebXML FAQ. I'd strike this entire sentence.]

UDDI and ebXML Registries may be used both within the organization and across organizations.

*"service" is a loaded word these days. **"arbitrary" connotes whimsical or meaningless; I don't think it's in our interest to state that we deal with "arbitrary" information. However, I do believe one of the most pertinent aspects of the ebXML Registry is that it shares information, and you don't mention that here. ***Is there a requirement somewhere that metadata registered in an ebXML registry be "standardized"? I don't believe so, except to the extent that it be useful to at least two parties, and they agree on both the semantic meaning and structural integrity of such metadata. However, I couldn't think of a modifier that encapsulated that idea. </Nicholas>

<Farrukh> ebXML Registry is a constituant part of the Electronic Business using XML (ebXML) standard, which develops standards and protocols to support business-to-business (B2B) operations. The ebXML Registry TC has defined a general purpose registry service for publishing and discovery of arbitrary content and standardized metadata, known as ebXML Reg/Rep. ebXML Reg/Rep is both a registry and a repository.

UDDI, managed by the UDDI Spec TC, is focused as a registry service for Web services and its artifacts.

Both UDDI and ebXML Registry may be used within the organization and across organizations. </Farrukh>

-----Original Message----- From: Anne Thomas Manes [mailto:an...@manes.net] Sent: Wednesday, January 14, 2004 7:12 AM To: Farrukh Najmi; reg...@lists.oasis-open.org Cc: Luc Clément Subject: Re: [regrep] UDDI FAQ entry on ebXML Registry

Farrukh,

Your characterization of UDDI is inaccurate. UDDI is a general-purpose registry. (We have a technical note that explains how to use UDDI as a registry for ebXML services.) It can also be used to register Web sites, Non-Web applications, schemas, namespaces, software assets, non-electronic services, etc. I know a number of users that use UDDI as a software asset management system.

Obviously there is a tremendous amount of overlap between the capabilities of the two registries. The one significant difference between the two is that RegRep is both a registry and a repository, and UDDI is only a registry.

Anne

At 10:02 AM 1/14/2004, Farrukh Najmi wrote:

Team,

The UDDI TC has the following question in their FAQ:

8. How does UDDI compare with the work of the OASIS ebXML Registry TC?

I was helping Luc scrub the answer to the question. With Luc's permission I post the latest answer below. The description below seems reasonable to me. Does any one have any comments?

My thanks to Luc for his responsiveness on this subject.

BTW maybe we should consider having the exact same question and answer in our FAQ (with Luc's permission)?

ebXML Registry is a constituant part of the Electronic Business using XML (ebXML) standard, which develops standards and protocols to support business-to-business (B2B) operations. The ebXML Registry TC has defined a general purpose registry service for publishing and discovery of arbitrary content and standardized metadata, known as ebXML Reg/Rep. ebXML Reg/Rep is both a registry and a repository.

UDDI, managed by the UDDI Spec TC, is focused as a registry service for Web services and its artifacts.

Both UDDI and ebXML Registry may be used within the organization and across organizations.

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to

http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to

http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets