eqd-29 is missing an else clause. The rule today is: ” eqd-29 (Mandatory) If integralMultipleExercise is present, (maximumNumberOfOptions / integralMultipleExercise ) must be a positive integer. Comment: When integral multiple exercise is present, maximum number of options exercised must be a positive integer multiple. ” The solution is to elevate the “if” clause to a … Continued
eqd-28 is missing an else clause. The rule today is: ” eqd-28 (Mandatory) Context: EquityMultipleExercise (complex type) If integralMultipleExercise is present, (minimumNumberOfOptions / integralMultipleExercise) must be a positive integer. Comment: When integral multiple exercise is present, minimum number of options exercised must be a positive integer multiple. ” The solution is to elevate the “if” … Continued
The rule eqd-15 is missing two else clauses. The problem is that this will lead to no result in some cases. The rule today is: ” Context: EquityExerciseValuationSettlement (complex type) eqd-15 (Mandatory) If equityValuation/valuationDate/adjustableDate exists, and equityEuropeanExercise exists, then equityValuation/valuationDate/adjustableDate/unadjustedDate must be equal to equityEuropeanExercise/expirationDate/adjustableDate/unadjustedDate. ” The proposed solution is to move the “if” clauses … Continued
eqd-6 is missing an else clause. The problem is that this causes eqd-6 to sometimes fail to produce a result. The rule today is: ” Context: equityBermudaExercise (complex type) eqd-6 (Mandatory) If latestExerciseTimeType is equal to SpecificTime then latestExerciseTime must be present. ” The proposed solution is to add the condition to the context: ” … Continued
eqd-3 is missing an else clause. The problem is that this causes eqd-3 to sometimes fail to produce a result. The rule today is: ” Context: EquityAmericanExercise (complex type) eqd-3 (Mandatory) If latestExerciseTimeType is equal to SpecificTime then latestExerciseTime must be present. ” The proposed solution is to add the condition to the context: ” … Continued
The structure “if then else” should be applied consistently. At the moment three rules deviate from this and use “if then otherwise”. All rules should use “if then else” consistently. The rules to fix are: Searching for: otherwise rules-english-ird.xml(17): The regular period of a set of calculation period dates is the period between a start … Continued
ird-29 has an if statement without an else clause. This means the result is undefined in some circumstances. The rule today is: ” Context: Calculation (complex type) ird-29 (Mandatory) If compoundingMethod exists then fixedRateSchedule must not be present. ” The proposal is to add a condition to the context: ” Context: Calculation (complex type)[exists(compoundingMethod)] ird-29 … Continued
The rule ird-25 is missing an else clause. The value is undefined in the case of step elements existing. The rule today is: ” Context: Schedule (complex type) ird-25 (Mandatory) If there are no step elements then initialValue must be non-zero. ” The proposed solution is to add a condition to the context. The rule … Continued
For rule ird-55: 1 – The context needs to be raised up to InterestRateStream so all the nodes refrred to are visible. At the moment resetDatesReference/@id may not be visible from the context. 2 – An additional condition must be added to check resetDatesReference exists. At the moment there is no else for the if … Continued
For rule ird-55: 1 – The context needs to be raised up to InterestRateStream so all the nodes refrred to are visible. At the moment calculationPeriodDates/@id may not be visible from the context. 2 – An additional condition must be added to check calculationPeriodDatesReference exists. At the moment there is no else for the if … Continued