FpML Issues Tracker

269: MessageRejected content model

December 5, 2006

closed

Major

Always

Schema

apparry

mgratacos

Summary

MessageRejected content model does not allow identification of the message which has been rejected by the sender of MessageRejected, the only content allowed at present is reason and additionalData, which also does not allow explicit identification of the system which rejected the message, as opposed to the system which is sending the MessageRejected message

Notes:

  • mgratacos

    03/05/07 6:04 pm

    “MessageRejected content model does not allow identification of the message which has been rejected by the sender of MessageRejected”

    Shouldn’t we use inReplyTo element to correlate them?

    Do you have any specific proposal to improve this content model?

    Thanks,
    Marc

  • matthew

    04/04/07 11:55 am

    The issue is how do you correlate the messages – M Gratacos

  • mgratacos

    08/01/19 11:41 am

    AWG 2019-08-01

    • Agreement to use inReplyTo to correlate the original message and the message rejected
    • Agreement to use sentBy, and sendTo to indicate the systems which is rejecting the message and to whom is rejecting it to.

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue