FpML Issues Tracker

309: Change integer to positive integer

February 14, 2007

closed

Crash

Always

Schema

Admin

mgratacos

Summary

The following types should be positiveInteger and not just integer:

fpml-asset.xsd(325): fpml-asset.xsd(371): fpml-cd.xsd(639): fpml-cd.xsd(644): fpml-eqd.xsd(433): fpml-eq-shared.xsd(1188): fpml-riskdef.xsd(25): fpml-shared.xsd(611): fpml-shared.xsd(1327):

Notes:

  • ggurden

    02/23/07 7:32 pm

    We should carefully review the context in which each of these elements is used because not all should necessarily be restricted to positiveInteger. For example, fpml-shared.xsd(1344): is used widely (for example in Rates) and it’s perfectly valid and necessary to support 0 and negative integer values. Indeed the documentation already states:

    A time period multiplier, e.g. 1, 2 or 3 etc. A negative value can be used when specifying an offset relative to another date, e.g. -2 days. If the period value is T (Term) then periodMultiplier must contain the value 1.

  • mgratacos

    03/08/07 3:38 pm

    AWG agreed to make these changes (not to periodMultiplier).

  • mgratacos

    03/08/07 5:40 pm

    Changes have been committed into the trunk. All FpML examples continue to pass schema validation.

    • 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