W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

RE: [hst] ebXML

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Thu, 25 Jul 2002 09:26:01 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C598E0@scidalmsg01.csg.stercomm.com>
To: "'Mark Baker'" <distobj@acm.org>
Cc: www-ws-arch@w3.org

Mark,

For me much of ebXML is not a theoretical discussion - having actually
implemented many of its elements, and found it a very rich and useful
framework 
from B2B point of view. Feel free to augment my report on ebXML with
comments such as below - I welcome it, though I am at the moment hard
pressed
for time to explore your comments further. I consider the purpose of the
ebXML report
served if it stimulates harvesting thoughts within HST. I am not expecting
WSA
to duplicate the enormous effort spent by domain experts in creating ebXML.
I do think, however, enabling ebXML or similar frameworks should be within
the scope of WS.

Cheers,

-Suresh
Sterling Commerce   



-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Thursday, July 25, 2002 12:04 AM
To: Damodaran, Suresh
Cc: www-ws-arch@w3.org
Subject: Re: [hst] ebXML


Suresh,

On Mon, Jul 22, 2002 at 02:34:02PM -0500, Damodaran, Suresh wrote:
> Components: Party, Role, Service, Actions, Collaboration Protocol Profile
> (CPP), Collaboration Protocol Agreement (CPA), Registry, Attachment.

My response to this is the same as to Hao's WSDL harvesting; those
are all roles which components can play (except for maybe Role and
Action? not sure).  We'd have to look at a deployment to see how
those roles are implemented in software.

> Connectors: Message Service Handler (MSH), Business Service Interface
(BSI)

I've thought hard about this one.  Yes, I think both of those contribute
to the semantics of an ebXML connector (as I understand the role of a
BSI), though they aren't themselves connectors.  But if we proceed along
these lines, I'd also count the implicit POST-like action on the ebXML
MS.  And the CPA, which defines the supported business transactions,
i.e. actions - so there's actually two actions for ebXML messages which
use a CPA, which is odd.

> Data Elements: ebXML Message, Business Process Specification, Business
> Document, Business Transaction, Binary Collaboration.

Except for the message itself, I think those are good examples of data
elements.

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com
Received on Thursday, 25 July 2002 10:25:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:02 GMT