FpML Issues Tracker

639: Remove no operation entries

March 5, 2008

closed

Major

Always

Architecture

apparry

mgratacos

Summary

FpML-4-X has an implicit confirmation view. No operation entries should all be removed, example

FpML-5-0 branch at revision 3382 file fpml-cd.xsd

This element contains all the terms relevant to defining the fixed amounts/payments per the applicable ISDA definitions.

FpML-4-4-4-WD-3 tag file fpml-cd.xsd

This element contains all the terms relevant to defining the fixed amounts/payments per the applicable ISDA definitions.

Attachments

  • Master Schema.doc

    • Notes:

  • mgratacos

    03/05/08 10:05 pm

    Apologies but I don’t understand this issue. What do you mean by ‘no operation’? the is making the element required in confirmation view.

  • apparry

    03/06/08 7:39 am

    Master schema should contain the default behaviour which is over ridden as required by a view. In the no operation cases, something which was mandatory in the prior implicit confirmation view is being made optional in the master schema, then being made mandatory again in the confirmation view, which is the only view where it is being used

  • andrew

    10/02/08 1:54 pm

    The master schema will be updated in line with the approach in the paper.

    AWG agreed on 02-10-2008 to close this issue.

  • mgratacos

    01/22/09 5:24 pm

    The default view is confirmation again. Annotations for reporting have been removed since the view hasn’t been developed yet. Annotations for pre-trade have been updated.

    • 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