FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
iyermakova
Summary
The validation rule ird-35 doesn't take into account schema optionality.
The correct behaviour is for the validation rule to take into account the schema.
The rule today is:
"
Context: PaymentDates (complex type)
ird-35 (Mandatory)
firstPaymentDate < lastRegularPaymentDate.
"
The problem is that both firstPaymentDate and lastRegularPaymentDate are not required elements.
A good example of this is the second PaymentDates in valid-ird-35-00.xml. The example is below.
The rules needs to be changed to take the schema into account.
Notes:
matthewdr
03/11/08 2:33 pm
The rule should be:
”
Context: PaymentDates (complex type)
ird-35 (Mandatory)
If firstPaymentDate exists and lastRegularPaymentDate exists, then firstPaymentDate < lastRegularPaymentDate. "
iyermakova
03/11/08 7:24 pm
The Val WG agreed to make the change to rule. The rule should be as above.
iyermakova
03/11/08 7:26 pm
The rule is now:
”
Context: PaymentDates (complex type)
ird-35 (Mandatory)
If firstPaymentDate exists and lastRegularPaymentDate exists, then firstPaymentDate < lastRegularPaymentDate. "
iyermakova
03/11/08 7:29 pm
The rule ird-35 is change for 4-4 (trunk/) and 5-0 (branches/FpML-5-0/)