FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
lyteck
Summary
The rule fx-46 uses an undefined term of "either" in conjunction with "or". The rule should use "or" as defined in the operators section.
The rule today is: " fx-46 (Mandatory) Context: SideRates (complex type) currency1SideRate/sideRateBasis = either "BaseCurrencyPerCurrency1" or "Currency1PerBaseCurrency". "
Solution 1 - using the union operator "|": fx-46 (Mandatory) Context: SideRates (complex type) currency1SideRate/sideRateBasis = ("BaseCurrencyPerCurrency1" | "Currency1PerBaseCurrency")
solution 2 - using precedence and logical operators: fx-46 (Mandatory) Context: SideRates (complex type) (currency1SideRate/sideRateBasis = "BaseCurrencyPerCurrency1") or (currency1SideRate/sideRateBasis = "Currency1PerBaseCurrency")
Notes:
lyteck
10/08/08 3:02 pm
fixed fx-46, fx-47 using solution 1. Added original wording as comments.
We don’t really have a section for approved boolean operators, do we?
matthewdr
10/08/08 3:20 pm
We have mathematical operators only. Of course we don’t define what they do, so what they do on a boolean type is undefined.