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] | [List Home]

Subject: [OASIS Issue Tracker] (EBXMLMSG-100) 5.1.8 RefToMessageId in Receipts

    [ https://issues.oasis-open.org/browse/EBXMLMSG-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66992#comment-66992 ] 

Sander Fieten commented on EBXMLMSG-100:

This sentence is indeed redundant from a specification perspective since the requirement to add the eb:RefToMessageId to the eb:MessagInfo is already in the Core, but I think it was added more a note to make clear that the copy of the eb:UserMessage inserted in the Receipt should not be used as reference to the acknowledged message. But this indeed isn't very clear even that there is no normative statement in this sentence.

Rereading this profiling rule I however see that there is another (and bigger) issue with it since the first sentence isn't correct as it states that the "sender of the Receipt MUST contain a copy of the eb:UserMessage ...". The sender of the Receipt however doesn't need to contain this copy, he must include it as content of the eb:Receipt element. 

Therefore I propose that the text of this profiling rule is changed as follows: 
"When a Receipt is to be used solely for reception awareness, the sender of the Receipt MUST include a copy of the eb:UserMessage structure of the received AS4 message as content of the Receipt, i.e. as child of the eb:Receipt element.

Note that the resulting Receipt now contains multiple reference to the user message, both in the eb:MessageInfo/eb:RefToMessageId element as well as in eb:Receipt. Only eb:RefToMessageId in the eb:MessageInfo group in the eb:SignalMessage SHOULD be used for referencing the received message."

> 5.1.8 RefToMessageId in Receipts
> --------------------------------
>                 Key: EBXMLMSG-100
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-100
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: AS4 Profile
>            Reporter: Pim van der Eijk
> Section of [EBMS3CORE] is clear that an ebMS3 Receipt MUST have a RefToMessageId referring to the MessageId of the received message.
> For no obvious reason, section 5.1.8 of AS4 repeats this in (a) for reception awareness receipts: 
> "The eb:RefToMessageId in the eb:MessageInfo group in the eb:SignalMessage contains the message identifier of the received message."
> This is redundant, and an implementer complains that this sentence has no MUST/ SHOULD/ MAY and therefore is poor specification language.
> Section 5.1.8 of AS4 does not repeat this in (b) for non-repudiation receipts, further confusing the developer.  
> The non-normative XSLT in Appendix B of AS4 generates a RefToMessageId for all receipts, whether reception awareness or NRR receipts. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]