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: T2 PLEASE READ - Suggested Change - add "From" Service and Actionto the header


William

Using RefToMessageId only solves part of the problem. Specifically it does
not solve the following ...
1. How does the recipient of a message know what to put in the Service and
Action for the message they return in the absence of a CPA (this is from the
Bank Payment example)
2. To use RefToMessageId, the sender of a message, where a reply is
expected, would have no option but to save the data from the EVERY message
even though the message was sent with deliverySemantics of BestEffort. This
should not be necessary. How can it be avoided?
3. If you are using PartyId, Service and Action to route a message, how do
you know which MSH at the Party should receive the message when Service and
Action have fixed values (as in an error message)? With the current spec, a
Party could only have one MSH ... even if it were IBM.

As stated before we need solutions to ALL the problems unless you think the
above are not problems.

Regards

David

-----Original Message-----
From: William J. Kammerer [mailto:wkammerer@novannet.com]
Sent: Monday, September 10, 2001 4:23 PM
To: ebXML Messaging (E-mail)
Subject: Re: T2 PLEASE READ - Suggested Change - add "From" Service and
Ac tionto the header


I agree with Bob Miller wholeheartedly on the issue of (not) adding
"From Service" and "From Action" elements to the Message Header.

David Burdett already gave the solution - and it is most elegant:  "[the
sender] would have to store information from the original message that
was sent and use the RefToMessageId to determine which application had
made the original Transfer Request."  So with reconciliation possible,
why require more and more junk to be added to the spec, especially that
which can easily be accommodated with programming? Therefore, I second
Bob and "...recommend the issue be dismissed without further action."

P.S., for those of us with short attention spans, could posters please
chop off extraneous junk (like the entire responded-to e-mail) and avoid
commenting "inline"?

William J. Kammerer
Novannet, LLC.



----------------------------------------------------------------
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