[OASIS Issue Tracker] Commented: (EBXMLMSG-16) AS4 Section 5.1.8 Generating Receipts Profiling Rule (a) interpretation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/EBXMLMSG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33437#action_33437 ] 

Theo Kramer commented on EBXMLMSG-16:
-------------------------------------

Option 2 requires the proposal as per EBXMLMSG-9

> AS4 Section 5.1.8 Generating Receipts Profiling Rule (a) interpretation
> -----------------------------------------------------------------------
>
>                 Key: EBXMLMSG-16
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-16
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: AS4 Profile
>         Environment: AS4 Profile 
>            Reporter: Theo Kramer
>            Priority: Minor
>
> Section 5.1.8 Generating Receipts Profiling Rule (a) of the AS4 spec reads as follows
> When a Receipt is to be used solely for reception awareness, the sender of the Receipt MUST contain a copy of the eb:UserMessage structure of the received AS4 message.
> This is open to misinterpretation as it could mean that either the receipt must contain a copy of the eb:UserMessage structure or the Sender must keep a copy of that. My thinking is that it should read as one the following
> 1  When a Receipt is to be used solely for reception awareness, the sender of the Receipt MUST retain a copy of the eb:UserMessage structure of the received AS4 message.
> or
> 2  When a Receipt is to be used solely for reception awareness, the sender must include a copy of the eb:UserMessage structure of the received AS4 message in the receipt.
> Comments or other suggestions ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira