FpML Issues Tracker

307: unobservable conversation completion

February 13, 2007

closed

Block

Always

Business Process

Admin

mgratacos

Summary

There are message exchanges in FpML for which the completion is unobservable. It is not apparent to an observer when there will be a follow-up message and when the exchange is completed.

For example, for the request quote it is not observable whether the interation completes with the RequestQuoteResponse, or whether there will be a future AcceptQuote. The way round this is to have a timeout event after a certain time period to complete the conversation. The timeout event needs to be specified in the message exchange.

Notes:

  • apparry

    03/07/07 11:32 am

    Resolution in the messaging branch, AJ will provide a commentary

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

  • matthew

    04/04/07 12:38 pm

    This can be observed on the expiration by the quotation manager.

  • matthewdr

    04/14/08 10:08 am

    Reassigning to BPWG.

  • mgratacos

    10/07/19 10:18 am

    Minutes AWG 2019-10-03

    • The definition of timeout is an implementation defined characteristic.
    • Timeouts are not defined by FpML.
    • The combination of service defined timeouts plus rejection message is enough for observing the completion.
    • Agreement to close the issue.

    • 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