|
Great
description Anne, Thanks for adding to the value of this
thread.
thanks,
Joel
Back
to the question at hand...
Let's
talk about design centers. Neither UDDI nor ebXML are intended to act as a
product catalog. They are intended to act as a service registry.
UDDI
is focused on Web services. A Web service is some piece of application
or business logic that runs somewhere on the Internet that is accessible through
a programmable XML interface. We're talking
about application-to-application communications, not human-to-application
interactions.
In
UDDI, you have a hierarchical structure that defines a business, the services
offered by the business, and some binding information that helps you figure out
how to communicate with each service. Your service might conform to a
service type ( tModel). For example, if your service conforms to a RosettaNet
PIP, you would associate your service with the tModel for that RosettaNet PIP.
Keep in mind that UDDI is a registry, not a registry/repository. Therefore the
metatdata about the services are stored elsewhere. The tModels and the
service bindings point to some exterior location where you will find metatdata
about the services (e.g., WSDL file, schema, written description, ebXML CPP,
etc.) UDDI does not define a method to specify the service
metadata.
ebXML
is aimed at helping businesses facilitate B2B interactions. ebXML's original
impetus was to develop a better, more powerful, more extensible way to perform
EDI. If doing business involves nothing more that simple Web-based ecommerce
(give me a credit card, and I'll ship the goods to your house), then ebXML might
be overkill. If doing business involves commissioning supplies, which need to be
delivered on a particular schedule, paid for using a purchase order, using a
negotiated discount rate, then ebXML is exactly what you're looking
for.
In the
ebXML reg/rep, you have a much richer data structure that you can use to
register and store information about your business, your services, your business
processes, your information models, etc. As Farrukh said,
the ebXML reg/rep spec does not specify how to describe your products or
services. It only specifies how to store your metadata in the repository and how
to query the registry to find those metadata. Other ebXML specs provide guidance
to help you describe your services. The ebXML business process spec specifies
how to model and describe your business process. In your business process
model, you describe the series of interactions (called choreography) that must
occur in order to complete a business transaction. Each interaction
involves an exchange of messages. You define schemas for these message formats.
The ebXML core components spec provides you with some low-level data entities
that you can use to specify the information model for these message formats.
Once you have completed your models, you create concrete XML specifications from
these models and store them as a "scenario" in the repository. Then you specify
the details of how to interact with your business process (protocols, security,
reliability, payment terms, etc.) in a Cooperative Protocol Profile (CPP). The
CPP points to your scenario specifications. The CPP and the scenarios all get
stored in the ebXML repository.
So
-- what I've described is the design center for these registries and
repositories. But you can do whatever you want with them. If you want to use
them as a product catalog, you may. Just remember that there are no
data elements within them to facilitate a product catalog.
Regards,
Anne
Thomas Manes
Sun
Microsystems
Joel,
I do agree that it sounds suspect
that the ability to define products within
ebXML is as you say,
suspect.
If I and others are mistaken, and this is possible then that
is ok.
However, the comments of newcomers to ebXML are important, and
if they can't
find the information easily, then maybe this needs to be
addressed.
For most businesses, the first question they ask is "How can
I use ebXML to
sell my products ?"
If there isn't any way to do
this, then it will take many, many years for
ebXML to ever catch on. Maybe
it will have another life and it's diagrams
will find their way into an
abstract art gallery.
*Products* like services, are *very* important to
business. It's very hard to do any sort of business in fact, if you have
nothing to sell, or even worse, no way to let customers know what you
have.
David Lyon
----- Original Message -----
From: Munter,
Joel D <joel.d.munter@intel.com>
To:
'David Lyon' <djlyon@one.net.au>;
<ebxml-discussion@lists.ebxml.org>
Sent:
Thursday, May 17, 2001 10:05 AM
Subject: RE: Help needed on using ebXML
Registry
> David
>
> I was simply trying to correct
Farrukh's representation of UDDI as a place
> to store "products."
I did not intend to make nor do I believe that I
made
> any statement
about ebXML's ability to do this. I wanted to clarify that
> UDDI
is a Registry for Services, not Products.
>
> The way that I read
Farrukh's remarks about ebXML is a little different.
It
> looks like
Farrukh is stating that the ebXML Registry services (ebRS)
>
specification DO NOT describe how to register products and services
within
> the ebXML Registry. I agree with you, this sounds
suspect. If this is
> true, then where is this defined within the
volume of ebXML
specifications.
>
> Joel
>
>
-----Original Message-----
> From: David Lyon [mailto:djlyon@one.net.au]
> Sent:
Wednesday, May 16, 2001 5:09 PM
> To: ebxml-discussion@lists.ebxml.org
>
Subject: Re: Help needed on using ebXML Registry
>
>
>
Joel,
>
> So are you saying that there is no way to define
products in ebXML ?
>
> This will be a major problem for business
users don't you think ?
>
> I mean, how can business use ebXML if
it can't cope with doing products ?
>
> Just a
thought.....
>
> David
>
> ----- Original Message
-----
> From: Munter, Joel D <joel.d.munter@intel.com>
>
To: 'Farrukh Najmi' <najmi@east.sun.com>; Rosita Marin
<rmarin@sodalia.it>
> Cc:
ebxml-discussion <ebxml-discussion@lists.ebxml.org>;
>
<ebxml-regrep@lists.ebxml.org>
>
Sent: Wednesday, May 16, 2001 12:04 AM
> Subject: RE: Help needed on
using ebXML Registry
>
>
> >
> > I apologize if
this addition/correction to Farrukh's reply is off-thread
> but
>
> I would like to make a slight correction. With respect to
Farrukh's
> > statement, "...Unlike other registries (e.g. UDDI), the
ebXML Registry
> specs
> > do not describe how products and
services are represented in the
> > registry...," I state the
following.
> >
> > The UDDI specification DO NOT DESCRIBE
how PRODUCTS are represented
within
> > the UDDI Registry.
>
> The UDDI specifications DO DESCRIBE how SERVICES are represented
within
> the
> > UDDI Registry.
> >
> >
Joel
> >
> > -----Original Message-----
> > From:
Farrukh Najmi [mailto:najmi@east.sun.com]
> >
Sent: Tuesday, May 15, 2001 5:59 AM
> > To: Rosita Marin
> >
Cc: ebxml-discussion; ebxml-regrep@lists.ebxml.org
>
> Subject: Re: Help needed on using ebXML Registry
> >
>
>
> > Rosita,
> >
> > In ebXML different
specifications address different aspects of the ebXML
> > B2B
architectural stack. The registry specs define how arbitrary content
>
> is published, discovered and retrieved from the registry using
the
> > interface described in Registry Services Spec (RSS version
1.0
> > http://www.ebxml.org/specs/ebRS.pdf
) and Registry Information Model
(RIM
> > version 1.0 http://www.ebxml.org/specs/ebRIM.pdf
).
> >
> > Unlike other registries (e.g. UDDI), the ebXML
Registry specs do not
> > describe how products and services are
represented in the registry. This
> > description of products,
services etc. are defined by other ebXML
> > specifications. For
example the Business Process Specification (
> > http://www.ebxml.org/specs/ebBPSS.pdf
)
> > defines how to represent business processes (generalization of
services)
> > in ebXML. I am not aware of any ebXML spec defining
product description.
> > The closest area may be Core Components
team. Registry clients are free
to
> > store any type of content
which allows for custom product descriptions
> > syntax and custom
product catalogs.
> >
> > Please let us know if you have any
more questions.
> >
> > --
> >
> >
Regards,
> > Farrukh
> >
> > Rosita Marin
wrote:
> >
> > > I am a newcomer to the ebXML world. In
these last two weeks I have
> > > been examining the specification
documents to understand if I can
> > > use ebXML in a trial
project we are currently developing.
> > >
> > > At
the moment I am trying to understand how products and services
> >
> are to be described in a ebXML Registry, and I have to say
> >
> that I am a bit confused. Basically I find it hard to understand
>
> > where I can find the necessary information to do what I
need.
> > > For the trial project I have to describe products and
services
> > > of a telecom service provider.
> >
>
> > > Probably a sort of road map in the documentation, to
find
> > > out the info I need, would be very helpful.
>
> >
> > > Thanks a lot for your help.
> >
>
> > > Regards,
> > >
> >
>
Rosita Marin
> > >
> > > --
> > >
>
> > ==========================================================
>
> > Rosita
Marin
fax : +39 0461 316 663
> > > Sodalia
S.p.A.
tel. : +39 0461 316 417
> > > Via Valentina Zambra
1 mailto: rmarin@sodalia.it
> > >
38100 TRENTO
> > > ITALY
> > >
==========================================================
> >
>
> > >
------------------------------------------------------------------
>
> > To unsubscribe from this elist send a message with the single
word
> > > "unsubscribe" in the body to: ebxml-discussion-request@lists.ebxml.org
>
>
> > --
> > Regards,
> > Farrukh
>
>
> >
> >
> >
------------------------------------------------------------------
>
> To unsubscribe from this elist send a message with the single
word
> > "unsubscribe" in the body to: ebxml-discussion-request@lists.ebxml.org
>
>
>
>
>
------------------------------------------------------------------
> To
unsubscribe from this elist send a message with the single word
>
"unsubscribe" in the body to: ebxml-discussion-request@lists.ebxml.org
>
>
>
------------------------------------------------------------------
> To
unsubscribe from this elist send a message with the single word
>
"unsubscribe" in the body to: ebxml-discussion-request@lists.ebxml.org
>
|