FpML Issues Tracker

851: ird-16 requires optional element to be present

September 18, 2008

closed

Minor

Always

Validation Rules

Admin

None

Summary

There is a problem with ird-16. The rules requires an optional element to be present.

The rule today is: " ird-16 (Mandatory) Context: CalculationPeriodDates (complex type) [isParametric] terminationDate/unadjustedDate > firstRegularPeriodStartDate. "

The problem is that //element(*, CalculationPeriodDates)/firstPeriodStartDate is optional.

Notes:

  • matthewdr

    10/21/08 1:25 pm

    Agreed to propose to Harry the addition of a guard on the existence of //element(*, CalculationPeriodDates)/firstPeriodStartDate.

  • h_mcallister

    10/30/08 10:17 am

    You mean, first*Regular*PeriodStartDate

  • matthewdr

    11/17/08 2:30 pm

    The correct form, incorporating Harry’s comment is:

    ”
    ird-16 (Mandatory)
    Context: CalculationPeriodDates (complex type)
    [isParametric][exists(//element(*, CalculationPeriodDates)/firstRegularPeriodStartDate)]
    terminationDate/unadjustedDate > firstRegularPeriodStartDate.
    ”

  • mgratacos

    11/25/08 2:08 pm

    Agreed to implement suggested solution. isParametric should be removed.

  • lyteck

    11/25/08 4:32 pm

    ird-16: implemented as agreed

  • matthewdr

    12/09/08 3:20 pm

    Closing after testing.

    • 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