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: RE: [ebxml-msg] toPartyMSH [was Re: Minutes 12/03/01 - Voting Meeting]

Actually Doug, you were around.  This was added after San Jose (October).


-----Original Message-----
From: Doug Bunting [mailto:dougb62@yahoo.com]
Sent: Tuesday, December 04, 2001 4:54 PM
To: ebXML Msg
Subject: [ebxml-msg] toPartyMSH [was Re: Minutes 12/03/01 - Voting


I wasn't around the TC when this was added to the specification but it
appears relatively clear.  The toPartyMSH encompasses the default actor and
also covers any other MSH legally able to respond on behalf of the To Party.
Good examples come from previous discussions of multi-hop ebXML-msh use
cases such as store-and-forward MSH instances in an enterprise DMZ.  From a
legal and technical perspective, it's perfectly fine for that MSH to
acknowledge a received message.

In my "first half" comments, I mentioned this was not completely apparent
from the text of our specification and recommended a few more words
describing this actor.  I also recommended requiring this actor value be
used only in the AckRequested and Acknowledgment elements.  According to the
rules we've defined, only the final destination MSH may eliminate
duplicates, re-order messages, et cetera.

Separately, I mentioned in various discussions about acknowledgments it
might be useful to allow the default actor to be named in these two
elements.  On second thought, I'm not so sure because the default actor is
already required to act in the fashion described for the toPartyMSH.  Other
than the words I mentioned above and re-adding use="required" to the
attribute references in the schema, nothing needs to change.

By the way, the actor you named isn't defined.  I'm assuming you meant the
default SOAP actor.


----- Original Message -----
From: "David Fischer" <david@drummondgroup.com>
To: "David Fischer" <david@drummondgroup.com>; "Christopher Ferris"
Cc: "Martin W Sachs" <mwsachs@us.ibm.com>; "Arvola Chan" <arvola@tibco.com>;
"ebXML Msg" <ebxml-msg@lists.oasis-open.org>
Sent: Tuesday, 04 December 2001 13:01
Subject: RE: [ebxml-msg] Minutes 12/03/01 - Voting Meeting

Sorry, I did not want to start a big discussion on the list over this -- but
managed to send to the list anyway.


-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Tuesday, December 04, 2001 2:47 PM
To: Christopher Ferris
Cc: Martin W Sachs; Arvola Chan; ebXML Msg
Subject: RE: [ebxml-msg] Minutes 12/03/01 - Voting Meeting

I'd rather not go to the list but can you explain why we need
urn:oasis:names:tc:ebxml-msg:service:toPartyMSH?  Isn't this the same as

- David.

<SNIP />

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

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

Powered by eList eXpress LLC