FpML Issues Tracker

305: Cannot distinguish Transport level messages from Business level messages

February 13, 2007

closed

Block

Always

Architecture

Admin

mgratacos

Summary

The FpML specification is unclear on the distinction between Transport Level and Business Level messages. For example, it is a generally received understanding, but remains unstated, that you cannot reject a rejectionMessagin.

Either we follow 20022 and FIX and treat this as distinct levels: Transport Level and Business Level, or we create some sort of definition of the relationships/constraints and correlations between the messages.

Notes:

  • apparry

    03/07/07 11:40 am

    BusML should be an adjunct schema to FpML

    This solution is in the bus2 branch

    JPM supports this ( AJ, AP, MR, HMcA )

  • matthew

    03/08/07 9:58 pm

    This is not a duplicate of 246.

    This issue is to separate Bus and Business messages into layers. Issue 246 is to define the missing messages.

  • matthewdr

    04/03/08 1:40 pm

    Agreed at the AWG that in Section 3.2.4 there should be a statement that a MessageRejected message may not be rejected.

    Agreed that AJ wil emend 3.2.4.

    We also agreed to review section 3.1.4.

  • matthewdr

    04/03/08 1:42 pm

    We could add a statement to the effect that implementers are responsible for detecting infinite loops.

  • andrew

    11/25/13 4:59 pm

    The messaging section has been substantially rewritten since this issue was raised. No further requests have been made to clarify the messaging architecture.

    This issue should be closed.

  • Leave an update

    You must be logged in to post an update.