FpML Issues Tracker

960: eqd-32 missing “satisfies” in quantification

June 18, 2009

closed

Minor

Always

Validation Rules

Admin

None

Summary

eqd-32 is currently: " Context: Contract (complex type) [//element(*, EquityDerivativeBase)/equityEffectiveDate] Every $equityDerivativeBase in //element(*, EquityDerivativeBase)[exists(equityEffectiveDate)] $equityDerivativeBase/equityEffectiveDate ge header/contractDate "

This is missing the term "satisfies". The correct XPath is: " Context: Contract (complex type) [//element(*, EquityDerivativeBase)/equityEffectiveDate] Every $equityDerivativeBase in //element(*, EquityDerivativeBase)[exists(equityEffectiveDate)] satisfies $equityDerivativeBase/equityEffectiveDate ge header/contractDate "

eqd-31 also needs changing in exactly the same way.

Notes:

  • matthewdr

    07/21/09 1:31 pm

    Discussed at the VWG today. Agreed to fix as proposed.

  • iyermakova

    07/21/09 5:36 pm

    In eqd-31 and eqd-32 rules added missing “satisfies” term in quantification.
    Committed the change to trunk/ (4-6) and branches 5-0

    • 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