FpML Issues Tracker

1053: Inconsistent element definitions

May 4, 2011

closed

Minor

Have not tried

Schema

Admin

mgratacos

Summary

In the MultipleExercise complex the type of the minimumNumberOfOptions element is xsd:nonNegativeInteger while the type of maximumNumberOfOptions element is NonNegativeDecimal.

I suspect the maximum value should also be a xsd:nonNegativeInteger.

Any comments?

Notes:

  • h_mcallister

    05/09/11 10:47 am

    Agreed: the type of maximumNumberOfOptions is xsd:nonNegativeInteger through the FpML 4-x series (4-3 to 4-9), consistent with minimumNumberOfOptions, so this looks like a drafting error at FpML 5-0.

    Can this be fixed as an erratum to the 5-x specifications (it is highly unlikely that any 5-x implementation depends on the ability to specify a non-integral maxmumumNumberOfOptions …)?

  • mgratacos

    09/06/19 5:07 am

    AWG 2019-09-05

    The issue was fixed so both minimumNumberOfOptions and maximumNumberOfOptions are now of type xsd:decimal.

  • mgratacos

    09/10/19 5:05 am

    Hi all,

    Yesterday we discussed issue 1053 regarding the type of minimum/maximumNumberOfOptions. As Brian indicated, the type was fixed within the EquityMultipleExercise and now both elements are of type xsd:decimal.
    However, after the call we noticed that we still have a minimumNumberOfOptions of type nonNegativeInteger within the PartialExercise.model (see element)
    I think we should also change the type of the minimumNumberOfOptions to xsd:decimal for the reasons we discussed yesterday (corporate actions that impact underlyer’s fraction, etc).
    Please let me know if you have any objections to this.
    Thanks,
    Marc

  • mgratacos

    09/10/19 5:13 am

    Changed the type of PartialExercise.model/minimumNumberOfOptions from NonNegativeInteger to NonNegativeDecimal to support fraction values due to corporate actions https://www.fpml.org/ticket/1053/

    The change will be published in version 5.11 Trial Recommendation (build 5)

    • 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