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

Pim van der Eijk created EBXMLMSG-100:

             Summary: 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]