[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ebxml-msg] CSD03 for AS4
That is a good explanation to add (so Theo it is for you to add to your upcoming comments). To be more specific on why "business receipt" and not just "receipt": - business receipts (when received) are supposed to go up the stack from message handler to application. - plain "receipts" (as in reliable messaging or acks) are not supposed to go up the stack: just for the messg handler to process and react to. -jacques -----Original Message----- From: Timothy Bennett [mailto:timothy@drummondgroup.com] Sent: Thursday, March 03, 2011 8:57 AM To: ebxml-msg@lists.oasis-open.org Subject: Re: [ebxml-msg] CSD03 for AS4 Assuming Jacques is OK with it, then yes it is OK with me. On 3/3/2011 4:41 AM, Theo Kramer wrote: > On 02 Mar 2011, at 11:00 PM, Timothy Bennett wrote: > >> The use of the phrase 'business receipt' in AS4 was to distinguish the nature of the AS4/ebMS3 receipt as being sufficient for NRR (non-repuation of receipt). In this sense it is very similar to the RFC3798 Message Disposition Notification response that is used by AS2 as a business receipt for non-repudiation. This receipt in AS4/ebMS3 contains the same information as the MDN, and thus distinguishes itself from the ebMS2 'acknowledgment' or web services reliable messaging acknowledgment. >> > Thanks - trust you would be ok if I 'lift' this and add it to the draft... > --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]