FpML Issues Tracker

355: Lucio’s questions

April 4, 2007

closed

Major

Always

Architecture

Admin

mgratacos

Summary

Marie,

I have some questions after reading the Service Description V5 doc. Apologies if prior discussions have already addressed them. In the ContractCreated notification, is the convention to use as the equivalent of a trade date, i.e. as "the date on which the parties agreed to the terms of the contract event"? I have found no usage documentation on , unlike in ContractNovated, and in contract increase and termination event notifications. I think it would be useful to add [Other Remaining Party] lines in the contract reference/version charts of section 7.2.2.3 to cover 4-way novations. Would that be feasible? There are some "trade" references like versionedTradeId and tradeDate in the doc. Are they residuals from previous doc versions? Regards, Lucio Iida Application Standards Integration Barclays Global Investors

Notes:

  • matthew

    04/04/07 1:30 pm

    Contract date needs to be defined in FpML.

    A 4 way novation is in FpML. Marie agrees to add to the SWIFT rulebook.

    The trade references are a SWIFT-ism. Thye have been corrected by Francoise.

  • matthew

    06/07/07 2:04 pm

    At the AWG meeting on 2007-06-07 it was agreed to rename this “tradeDate” in the 5.0 branch.

  • matthew

    06/07/07 2:05 pm

    This should be renamed now in the 5.0 branch.

  • mgratacos

    06/07/07 4:41 pm

    contractDate should be renamed tradeDate in the 5.0 branch. The current schema’s documentation should be updated making clear that contractDate corresponds to the tradeDate and that the name of the element will be changed in version 5.0.

  • mgratacos

    06/08/07 4:20 pm

    Documentation has been added and committed to the trunk.

  • mgratacos

    06/11/07 9:27 am

    Change has been committed to the 5.0 branch.

  • Leave an update

    You must be logged in to post an update.