OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [ebxml-msg] Re: [ebxml-cppa] Proposed schema changes,plus illustrative examp le


The purpose of the ebXML MS protocol is to get a message from the From
Party to the To Party. So, in your terms, the MS protocol sends the message
from an instance of X, a "party", to an instance of X, a "party".

At the ebXML messaging layer, the message is sent to an endpoint address
which is typically a URL that represents the To party.  It is the endpoint
address given in the delivery channel  that is associated in the CPA (or
equivalent) with the desired service and action.

The X's are NOT instances of MSHs.  The message goes to a (persistent)
store above the upper boundary of the MSH and then is routed to the desired
application software entry point.

From what I recall, we have never attempted to formally define an instance
of an MSH. As I said in my previous posting, I don't believe any of the
existing identifiers is suitable unless you want to consider PartyId.CPAId.

As far as I can see, the only use for defining an instance of a MSH would
relate to error handling.  However it is not clear to me that this is the
business of the MS specification.  Error handling is much more likely the
business of system configuration and management software inside each node.



Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com

Dan Weinreb <dlw@exceloncorp.com> on 10/27/2001 12:09:42 AM

Please respond to "Dan Weinreb" <dlw@exceloncorp.com>

To:    Martin W Sachs/Watson/IBM@IBMUS
cc:    Jzheng@vitria.com, dmoberg@cyclonecommerce.com,
       ebxml-cppa@lists.oasis-open.org, ebxml-msg@lists.oasis-open.org
Subject:    Re: [ebxml-cppa] Proposed schema changes, plus illustrative
       examp      le

   Date: Fri, 26 Oct 2001 23:16:32 -0400
   From: "Martin W Sachs" <mwsachs@us.ibm.com>

                                                It isn't obvious
   to me that any of the identifiers, endpoint addresses, or names that we
   have been discussing is appropriate for labelling a single MSH.

Surely the purpose of the ebXML MS protocol is primarily to get a message
from one point to another point.

When an application program utilizes a software library that
implements the MS protocol, the application program surely must say to
the software library "Here is a message, please send it to X", and
the job of the protocol is to get the message to X.

So there must be some answer to the question, what is X an instance
of?  And also, how are such instances named, what is the syntax for
such names, what is the namespace from which such names are drawn?

In the case of the Internet Protocol (IP), X is an instance of an
Internet Host.  They are named by IP addresses, whose syntax is a
32-bit unsigned integer.  There must be analogous answers for the
ebXML MS protocol.

I have been assuming that X's are instance of MSH's.  The naming is
still unclear.  But it seems to me that there simply has got to be
some common understanding of what X is an instance of, and how such
instance are named, in order for anyone to do anything useful with
an implementation of ebXML MS.

-- Dan

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC