FpML Issues Tracker

831: ref-38 needs a more specific context

September 17, 2008

closed

Minor

Always

Validation Rules

Admin

None

Summary

The rule ref-38 needs a more specific context.

A second issue is that the element //element(*, MandatoryEarlyTermination)/cashSettlement/cashSettlementValuationDate is an optional element.

The rule today is: " ref-38 (Mandatory) Context: MandatoryEarlyTermination (complex type) The cashSettlement/cashSettlementValuationDate/dateRelativeTo/@href attribute = the @id attribute of an element mandatoryEarlyTerminationDate. "

The rule should probably be: " ref-38 (Mandatory) Context: MandatoryEarlyTermination (complex type)/cashSettlement/cashSettlementValuationDate/dateRelativeTo name(id(@href)) eq xs:string("mandatoryEarlyTerminationDate"). "

There is a more fundamental problem, that this rule would resolve to any element named "mandatoryEarlyTerminationDate" in the document. For a document containing more than one 'trade' such as a Valuation, this rule just doesn't make sense. The scope of the rule needs rethinking.

Notes:

  • matthewdr

    12/09/08 2:23 pm

    Agreed at the VWG to implement the proposal.

  • lyteck

    12/09/08 8:38 pm

    implemented as agreed and updated English Description accordingly:

    ref-38 (Mandatory)
    Context: MandatoryEarlyTermination (complex type) /cashSettlement/cashSettlementValuationDate/dateRelativeTo

    English Description:
    The cashSettlement/cashSettlementValuationDate/dateRelativeTo/@href attribute is equal to the @id attribute of an element mandatoryEarlyTerminationDate

    Formal Description:
    name(id(@href)) eq xs:string(“mandatoryEarlyTerminationDate”)

  • matthewdr

    12/10/08 10:12 am

    Tested, passed, closing.

  • Leave an update

    You must be logged in to post an update.