RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in Vancou ver

["Nieman, Scott" <Scott.Nieman@NorstanConsulting.com>]

I am hoping that the OASIS / ebXML issues be resolved before then.
Scott

-----Original Message-----
From: Scott Hinkelman [mailto:srh@us.ibm.com]
Sent: Monday, February 19, 2001 9:02 AM
To: Nieman, Scott
Cc: Munter, Joel D; ''ebxml-regrep@lists.ebxml.org' '; Joel Farrell; Dan
Wolfson; Josephine Cheng; Don Haderle; Dan Chang; 'Jonathan Dayao '
Subject: RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in
Vancou ver


Scott N. / RegRepers,

One of the main points in my presentation was to negate the popular
thinking that UDDI and
ebXML/OASIS Registry efforts "look like they are doing the same thing",
which has proliferated
widely from what I see as casual observations.

UDDI and ebXML/OASIS efforts do have overlap in the general idea of
"discovery", one area
common to any effort adressing underpinnings of eMarketplace concepts.
Beyond that general concept, and even within that discovery area, there are
clear differences,
and I outlined how these two efforts will likely coexist.

Fundamentally, I believe there needs to be analysis between ebXML Registry
and the
OASIS Registry for any logical convergence, as these are much closer
together that UDDI.
The result would almost certainly NOT make sense to "converge" with UDDI.

A summit could ultimately be a good idea to address formal UDDI
"coexistence", but I suggest a work effort
to analyze ebXML Registry with OASIS Registry first.

Thanks,
Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



"Nieman, Scott" <Scott.Nieman@NorstanConsulting.com> on 02/19/2001 07:45:11
AM

To:   "Munter, Joel D" <joel.d.munter@intel.com>,
      "''ebxml-regrep@lists.ebxml.org' '" <ebxml-regrep@lists.ebxml.org>
cc:   Joel Farrell/Cambridge/IBM@IBMUS, Dan Wolfson/Austin/IBM@IBMUS,
      Josephine Cheng/Santa Teresa/IBM@IBMUS, Don Haderle/Silicon
      Valley/IBM@IBMUS, Dan Chang/Santa Teresa/IBM@IBMUS, Scott
      Hinkelman/Austin/IBM@IBMUS, "'Jonathan Dayao '"
      <Jonathan@CCS.dlsu.edu.ph>
Subject:  RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in Vancou
       ver



Joel, your are correct, and perhaps the distributed architecture IS the
point of convergence for UDDI, ebXML and OASIS.  ebXML has had a
distributed
registry model in mind from its inception, written in the Requirements
specification, Technical Architecture specification, and the Registry
Business Domain specification ( use cases ).  However, the implementation
specifications ( Registry Services and Registry Information Model ) do not
have this detailed.

In the January ebXML Registry f2f meeting at Sun in Burlington, MA, we
agreed that the next f2f would be hosted by Norstan in Minneapolis.  I
would
like to entertain that this f2f be a "Registry Summit" to kick off the
UDDI/ebXML/OASIS convergence conversation.  I am proposing April 9-11 which
should be nice spring time weather.  Please announce this to the UDDI folks
so that we can nail down the logistics.  Personally I prefer a M-W meeting,
but if M-F is warranted, I can be convinced especially if is to dedicate
time to complete specifications.  If the week is going to pose a conflict,
I
am flexible in April.  But I do believe it should be in early to mid April
to move this concept nicely into the May ebXML meeting in Vienna.

Best regards,

Scott


-----Original Message-----
From: Munter, Joel D [mailto:joel.d.munter@intel.com]
Sent: Friday, February 16, 2001 10:49 AM
To: 'Nieman, Scott'; 'Jonathan Dayao '; ''ebxml-regrep@lists.ebxml.org'
'
Cc: 'Joel Farrell '; 'Dan Wolfson '; 'Josephine Cheng '; 'Don Haderle ';
''Dan Chang' '; 'Scott Hinkelman '
Subject: RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in
Vancou ver


reply:

Within its initial Version 1 specification UDDI relies on replication to
ensure that all queries are satisfied consistently, completely, and as
quickly as possible from any UDDI Operator Node.  Please note, Version 1 of
UDDI is up and running today.

Within the current UDDI model, businesses register information about the
business and details about their web services at one of the (replicating)
Operator Nodes.  The "owner" of the data maintains their data on that
Operator Node.  This can be done through a well defined API or through a
Web-based user interface.

The UDDI effort is going through several more specification version cycles.
Discussions of Replication vs. a Distributed Architecture will continue
into
the subsequent iterations of the UDDI specifications.  Version 2 is
scheduled to start a UDDI Advisor Group Review Cycle in the next few weeks.

Both of the architectures and approaches currently specified in ebXML and
UDDI, and briefly described by Scott and I, have their advantages and
disadvantages.  I look forward to seeing and how both efforts mature.  I
envision an interoperable environment in the future.

Joel Munter
Intel Corporation
joel.d.munter@intel.com
(480) 552-3076


-----Original Message-----
From: Nieman, Scott [mailto:Scott.Nieman@NorstanConsulting.com]
Sent: Friday, February 16, 2001 7:08 AM
To: 'Jonathan Dayao '; ''ebxml-regrep@lists.ebxml.org' '
Cc: 'Joel Farrell '; 'Dan Wolfson '; 'Josephine Cheng '; 'Don Haderle ';
''Dan Chang' '; 'Scott Hinkelman '
Subject: RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in
Vancou ver


The ebXML Registry is intended to be distributed, in fact, support a
peer-to-peer (P2P) model in the next iteration.  Replication is an
antiquated concept except for service providers who need fail safe
operations, and this represents a fundamental difference between the UDDI
and ebXML architecture.  ebXML Registry is focusing on a distributed model
which the "owner" of the content can ultimately maintain its own
information
in its own registry and create associations (links) to external objects
residing in other registries.

Therefore in concept it is feasible for a given business to maintain its
own
profile (as part of its web site) that references its business processes,
data formats exchanged within those business processes, communication
protocols etc.  These process definitions may be associated to standard
business process patterns in another registry such as OASIS, X12, OMG, etc.


The ebXML Registry pub/sub architecture will enable distributed queries.

Scott

-----Original Message-----
From: Jonathan Dayao
To: 'xmledi-group@disa.org'; 'Dan Chang'; Scott Hinkelman
Cc: Nieman, Scott; Joel Farrell; Dan Wolfson; Josephine Cheng; Don Haderle
Sent: 2/15/01 8:15 PM
Subject: RE: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in Vancou
ver

I am new to these topics.  I fully support the suggestion and I hope one
approach will come out after the discussions.  It is difficult to hop
from one material to the other just to get a grasp of what they are all
about.

Also, is the registry centralized in the sense that those who want to do
transactions over the net need to register somewhere?  Can't a company
just put up its company profile and business processes in its own web
site.  In this case, searching for trading partners may be assisted by
search engines.  I read in one of the materials that the registry is
logically centralized but physically distributed however I am wondering
about the reason why companies need to register somewhere...or do they?
I might be missing something.  Will someone please clarify or give
pointers to other reading materials.  Thank you very much in advance for
the help.

Jonathan

-----Original Message-----
From: Dan Chang [ mailto:dtchang@us.ibm.com <mailto:dtchang@us.ibm.com>
]
Sent: Friday, February 16, 2001 3:02 AM
To: Scott Hinkelman
Cc: Nieman, Scott; 'ebxml-regrep@lists.ebxml.org '; Joel Farrell; Dan
Wolfson; Josephine Cheng; Don Haderle
Subject: Re: IBM UDDI / ebXML / OASIS presentation given 2/14/01 in
Vancouver



Scott,

I am very glad to see that initial discussions have started, in the
ebXML
Vancouver meeting, on UDDI, OASIS and ebXML registries. Your
recommendation
to form a task force looking into aligning UDDI and ebXML registries is
a
very good one and should benefit the industry and customers. As an
implementer of registry, I would like also to recommend that a task
force
be formed looking immediately into merging the ebXML Registry
Information
Model/Services specification with the OASIS Registry/Repository
Technical
Specification. This will additionally benefit the industry and
customers.

Regards,  Dan

e-business Data Technology and Standards
IBM Silicon Valley Laboratory
Notes:     Dan Chang/Santa Teresa/IBM@IBMUS
Internet:  dtchang@us.ibm.com
VM:          IBMUSM50(DTCHANG)
Phone:    (408)-463-2319


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-regrep-request@lists.ebxml.org


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-regrep-request@lists.ebxml.org