FpML Issues Tracker

625: cd-8 context too high up

March 1, 2008

closed

Minor

Always

Validation Rules

Admin

mgratacos

Summary

The context for evaluating cd-8 is too high up in the document.

The rule today is: " Context: GeneralTerms (complex type) cd-8 (Mandatory) Preconditions: LongForm scheduledTerminationDate/adjustableDate/eAdjustments or scheduledTerminationDate/adjustableDate/dateAdjustmentsReference must be present. "

The rule could be rewritten with a more specific context: " Context: //element(*, GeneralTerms)/scheduledTerminationDate/adjustableDate cd-8 (Mandatory) Preconditions: LongForm dateAdjustments or dateAdjustmentsReference must exist. "

NB I have provide the context in XPath because the current style used by the Validation Rules is undefined for contexts like these.

Notes:

  • matthewdr

    04/08/08 1:40 pm

    Or change the rule to:

    Context: GeneralTerms (complex type)
    cd-8 (Mandatory)
    Preconditions: LongForm
    If scheduledTerminationDate exists, then scheduledTerminationDate/adjustableDate/eAdjustments or scheduledTerminationDate/adjustableDate/dateAdjustmentsReference must be present.

  • matthewdr

    04/08/08 1:42 pm

    Or change the rule to:

    Context: GeneralTerms (complex type) [scheduledTerminationDate]
    cd-8 (Mandatory)
    Preconditions: LongForm
    If scheduledTerminationDate exists, then scheduledTerminationDate/adjustableDate/eAdjustments or scheduledTerminationDate/adjustableDate/dateAdjustmentsReference must be present.

  • matthewdr

    04/08/08 1:44 pm

    Agreed at VWG to take the rules as:

    Context: GeneralTerms (complex type)
    cd-8 (Mandatory)
    Preconditions: LongForm
    If scheduledTerminationDate exists, then scheduledTerminationDate/adjustableDate/eAdjustments or scheduledTerminationDate/adjustableDate/dateAdjustmentsReference must be present.

  • matthewdr

    04/08/08 1:44 pm

    Agreed at VWG to authorize Marc Gratacos to implement.

  • mgratacos

    04/22/08 9:00 am

    This has been committed to the trunk (revision 3646) and to the 5.0 branch (revision 3647)

  • Leave an update

    You must be logged in to post an update.