FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
danieldui
Summary
The rule ird-25 says:
Context: Schedule (complex type) If step does not exist, then initialValue must not be equal to 0
In the test case the fixedRateSchedule is defined as:
But to trigger the rule it must be changed to:
If have checked back to FpML 4.2 and it has never been correct.
Notes:
adingwal
03/29/11 1:46 pm
I have had a look at this test case.
The rule is intended to be exercised by:
0
DEM
Back in FpML 4.2 this did work as notionalStepSchedule was derived from Schedule. However, since then, the type notionalStepSchedule is derived from has been changed to NonNegativeSchedule. As a result, this test case no longer exercises the rule.
I can’t see a corresponding rule for NonNegativeSchedule so it looks like thre is also a rule missing now.
iyermakova
03/30/11 7:00 pm
I agree. The invalid-ird-25 test-case is correct. The rule is for the notional schedule. The context of the rule-25 needs to be updated from “Schedule” to “NonNegativeSchedule” to reflect the schema change.
danieldui
04/19/11 3:00 pm
iyermakova
04/20/11 7:01 pm
As per my action item, created a new ird-61 rule (similar to ird-25) to handle a new NonNegativeSchedule complex type. The change was committed to branches/FpML-5-2
iyermakova
05/10/11 6:31 pm
Added:
– corrected invalid-ird-25-01.xml for rule ird-25
– new invalid-ird-61-01.xml for new rule-ird-61
Committed to branches/FpML-5-2.
It will be published with FpML-5-2-WD1 publication
danieldui
05/24/11 1:37 pm
see notes