RE: [ebxml-dev] Question about DeliveryReceipt andAcknowledgmentmessage

[David Fischer <david@drummondgroup.com>]

How the routing is performed to send to an intermediary rather than to the
intended recipient is not specified in ebXML-MS.  You would probably need to
build routing tables although it is more likely that you would always send
everything to a VAN (Ariba, C1, etc.) and let them figure out how to send to the
end.

There may be multiple AckRequested elements (zero, one or two) requesting an
Acknowledgment from either the nextMSH, the end, or both.

More routing fields (something like a routeThrough parameter) will be discussed
for the next version (v3.0?).

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Bell Stephen [mailto:stephen.bell@cpgmarket.com]
Sent: Wednesday, January 30, 2002 2:30 AM
To: David Fischer; Dick Brooks; Lee, Teho; Ebxml-Dev (E-mail); ebMXL MS
(E-mail)
Cc: Ian Jones
Subject: RE: [ebxml-dev] Question about DeliveryReceipt and
Acknowledgmentmessage


If Acknowledgement is to confirm next-hop (in a multi-hop scenario), how
does ebXML allow us to complete a multi-hop? Are there specific fields
used for the routing (for each hop instance) or is this not defined at
the moment?

I fail to see how it is possible to have a multi-hop scenario with an
messaging intermediary with the current message structure.

Regards,
Stephen Bell

-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: mercredi, 30. janvier 2002 04:10
To: Dick Brooks; Lee, Teho; Ebxml-Dev (E-mail); ebMXL MS (E-mail)
Cc: Ian Jones
Subject: RE: [ebxml-dev] Question about DeliveryReceipt and
Acknowledgmentmessage


Dick is correct.

In v1.0, DeliveryReceipt was end-to-end and Acknowledgment was next-hop.
DeliveryReceipt was deleted for v2.0 and Acknowledgment was used for
both
end-to-end and next-hop (with the use of an actor).

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Dick Brooks [mailto:dick@tech-comm.com]
Sent: Tuesday, January 29, 2002 7:34 PM
To: Lee, Teho; Ebxml-Dev (E-mail); ebMXL MS (E-mail)
Cc: Ian Jones
Subject: RE: [ebxml-dev] Question about DeliveryReceipt and
Acknowledgment message


Teho,

I don't know if the semantics have changed between V1.0 and 2.0 but in
V1.0
a Delivery Receipt was used to indicate a message was "delivered" to a
backend application, whereas an "Acknowledgement" indicates successful
delivery of a message between MSH's, nothing more.

Have these semantics changed with V2.0?


Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>
Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714


-----Original Message-----
From: Lee, Teho [mailto:TLee@iona.com]
Sent: Tuesday, January 29, 2002 3:02 PM
To: Ebxml-Dev (E-mail); ebMXL MS (E-mail)
Subject: [ebxml-dev] Question about DeliveryReceipt and Acknowledgment
message


Hi,

In ebXML MS spec v1.18, line 1408, it says "The Delivery Receipt
mechanism
MAY also be used to perform End-to-End Reliable Messaging by acting as
an
Acknowledement Message.".

To me, the Acknowledgment message is like a functional ack to be sent
only
if the message received is structurally correct. While the
DeliveryReceipt
is a MSH-level ack which will be sent, if requested, regardless of the
correctness of the original message. If this is correct, potentially as
a
sender of the original request message, I may receive a DeliveryReceipt
message and later an Acknowledgment(as positive ack) or an ErrorList
message(as negative ack). I'm wondering if the spec actually means the
DeliveryReceipt element, if requested, is to be part of Acknowledgment
message.

Could someone shed some light on this?

[Legends]
DeliveryReceipt message: message containing DeliveryReceipt element.
Acknowledgment message: message containing Acknowledgment element.
ErrorList message: message containing ErrorList element.


Teho Lee

IONA
END 2 ANYWHERE
Tel (408) 350-9533


----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>


----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>


----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>

----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>