[regrep] FW: [uddi-spec] Technical Note:"UDDI as the registry for ebXML c omponents"

["Breininger, Kathryn R" <kathryn.r.breininger@boeing.com>]

fyi
-----Original Message-----
From: Munter, Joel D [mailto:joel.d.munter@intel.com]
Sent: Tuesday, October 29, 2002 4:37 PM
To: 'Keisuke Kibakura'; uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] Technical Note: "UDDI as the registry for ebXML
c omponents"



kibakura-san,
as one of the original sources of this draft that needs "much rework," I am
happy to see the effort continue.  good luck!  
joel

-----Original Message-----
From: Keisuke Kibakura [mailto:kibakura@jp.fujitsu.com]
Sent: Monday, October 28, 2002 3:27 AM
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] Technical Note: "UDDI as the registry for ebXML
components"


All, 

Below are the background and purposes of the TN titled "UDDI as the 
registry for ebXML components", which I presented at the last 
conference call. 

I'm ready to author this note. Editors/reviewers/contributors are needed.
Anyone who is interested in this activity, please notify me and post to
the list. 

Any comments are welcome. 

Regards,

--
Keisuke Kibakura


------------
Title of TN: 

"UDDI as the registry for ebXML components"

Background:

Some standard bodies has initiated pilot projects that use ebXML 
framework for business-to-business transactions.  And some companies 
are getting started to use (some) ebXML technologies for their businesses.
While the uses of web service technologies in the real business field
are greatly expanding, such requirements should not be ignored that 
some companies want to register their ebXML-based services and/or
locations of their ebXML components (CPPs, BPSS definitions, ...) to 
a UDDI registry.  A recommended way of modeling a service which is 
conformant to ebXML specifications is needed. 

Purposes of the TN are:

- to describe the ways to register ebXML-conformant services to a UDDI 
  registry.  Some steps could be involved, such that:

  * a standardization body creates and registers some tModels which 
    represent its standardized business processes. 

  * a company creates businessServices/bindingTemplates, associates
    them with tModels, and register them to a UDDI registry 

- to describe the way to use a UDDI registry to search for ebXML 
  components such as CPP (Collaboration Protocol Profile) and BPSS
  (Business Process Specification Schema).

- to define a set of common tModels which relate to ebXML specifications.
  (Probably such common tModels should be registered to the UDDI Business 
  Registry.)

And this TN does not intend to: 

- show the migration way of UDDI registry and ebXML Reg/Rep.  This TN 
  is just a guidance for use of a UDDI registry with *some* of ebXML 
  components.

About the existing draft:

It could be posssible to use the current draft document
http://www.oasis-open.org/committees/uddi-spec/doc/draft/tn-ebxml-taxonomy.d
oc
as a starting point.  But it needs much rework. 


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>