MHonArc v2.5.2 -->
















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: RE: RefToMessageId in DR & Ack




From: "Burdett, David" <david.burdett@commerceone.com>
To: 'David Fischer' <david@drummondgroup.com>,ebXML Msg <ebxml-msg@lists.oasis-open.org>
Date: Mon, 08 Oct 2001 17:23:58 -0700






Title: RE: RefToMessageId in DR & Ack





You are probably right. However, that's not the main reason for doing this. I think the main reason is for when the delivery receipt or acknowledgement is digitally signed. By putting the RefToMessageId in a separate element you can directly bind all the data in the Delivery Receipt/Acknowledgement together.

David


-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Monday, October 08, 2001 12:49 AM
To: ebXML Msg
Subject: RefToMessageId in DR & Ack



Since a DeliveryReceipt element or an Acknowledgement element can be on any
message, do they need their own RefToMessageId elements since the RefToMessageId
in the MessageHeader might be in use by something else?


I am tempted to say that they would never be on a message in which the
RefToMessageId would be different, yet is it really never?


Regards,


David Fischer
Drummond Group



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