FpML Issues Tracker

Summary

cd-26 does not handle the effectiveDate being optional.

cd-26 today is: " Context: CreditDefaultSwap (complex type) [exists(feeLeg/singlePayment/adjustablePaymentDate)] feeLeg/singlePayment/adjustablePaymentDate gt generalTerms/effectiveDate/unadjustedDate "

There is a guard on paymentDate, there should also be a guard on effectiveDate. I propose the new rule be: " Context: CreditDefaultSwap (complex type) [exists(feeLeg/singlePayment/adjustablePaymentDate)][exists(generalTerms/effectiveDate)] feeLeg/singlePayment/adjustablePaymentDate gt generalTerms/effectiveDate/unadjustedDate "

I do not know the scenarios under which generalTerms/effectiveDate may be optional. The schema fails to document what it means when the field is not present. We should also get the schema documentation fixed up to state what it means when the element is not present.