FpML Issues Tracker

862: Knock complex type should force at least one of knockIn or knockOut

October 21, 2008

closed

Minor

Always

Equity Derivatives

Admin

apparry

Summary

The design of the Knock type and its usage with an optional element of the OptionFeatures type means that it is possible to define an equityOption or equityOptionTransactionSupplement that contains a knock feature but omits any definition of the knock in/out levels.

e.g.

... ... ... ...

I suggest that the model for Knock type be changed to an 'at least one of' pattern ((knockIn,knockOut?)|knockOut).

Strictly speaking this change would not be backwards compatible. It could be enforced with additional validation rules in the short term.

Notes:

  • mgratacos

    01/24/20 6:45 am

    AWG 2020-01-23
    We should update the type and add an “at least one” pattern.
    Agreed to fix it even if it’s not a backward compatible change.

  • mgratacos

    03/30/20 6:27 am

    This has been fixed in FpML 5.11 Recommendation build 8.

    • 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