FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
None
Summary
fx-13 should be written out as per the FpML rule specification guidelines. The rule today is: " fx-13 (Mandatory) Context: FxAverageRateOption (complex type) [exists(averageRateObservationDate elements)] Each observedRates/observationDate should match one of the dates defined by averageRateObservationDate/observationDate. "
1. The use of "should" must be replace with something stronger (like "must"). 2. The function "match" is not defined and not written out as a function. There is a function named "match", but this isn't its definition. 3. "exists(averageRateObservationDate elements)" is invalid function syntax.
The proposal to write it out as per the guidelines is: " fx-13 (Mandatory) Context: FxAverageRateOption (complex type) [exists(averageRateObservationDate)] every $observationDate in observedRates/observationDate satisfies $observationDate = averageRateObservationDate/observationDate Comment: Each observed rate date must have a corresponding average rate observation date . "
Notes:
lyteck
09/16/08 3:09 pm
valwg (2008-09-16):
1. agreement to change from “should” to “must”
3. will fix function syntax to remove extraneous “elements”
agreement to not change rule definition further – see related issue 806
lyteck
09/30/08 7:50 pm
Fixed as agreed in previous note (Lyteck 2008-09-16)