712: cd-37 firing too often, some of the rule should be in the context

The rule cd-37 is firing too often – i.e. firing outside of its business scope. Some of the rule body should be in the context. The rule today: ” Context: CashSettlementTerms (complex type) cd-37 (Mandatory) Preconditions: SameCurrency quotationAmount/amount >= minimumQuotationAmount/amount, if both elements are present. ” The proposed rule written out in the FpML style: … Continued

710: Context of cd-3b needs to change to reflect schema changes

The context of cd-3b needs to change to reflect changes in the schema. The rule today is: ” Context: Trade (complex type) cd-3b (Mandatory) Preconditions: ISDA1999 The content of documentation/ContractualTermsSupplement must not begin with the string ISDA2003Credit. ” However ContractualTermsSupplement is a repeating element following recent schema changes: ” DEPRECATED – This element will be … Continued

709: cd-3b is missing a precondition on presence of optional element

The validation rule cd-3b is missing a precondition on the prescence of an optional element. Th rule today is: ” Context: Trade (complex type) cd-3b (Mandatory) Preconditions: ISDA1999 The content of documentation/ContractualTermsSupplement must not begin with the string ISDA2003Credit. ” The problems are: 1. documentation is optional. 2. contractualTermsSupplement is optional. 3. contractualTermsSupplement has an … Continued

708: cd-1b has a redundancy in a rule

The rule cd-1b has a redundancy in the expression of the rule. unadjustedDate is a mandatory field of creditDefaultSwap/generalTerms/effectiveDate, so it does not needed to be tested for existence. The rule today is: ” Context: Trade (complex type) cd-1b (Mandatory) Preconditions: CreditIndex If creditDefaultSwap/generalTerms/effectiveDate/unadjustedDate is present, tradeHeader/tradeDate must be equal or after creditDefaultSwap/generalTerms/effectiveDate/unadjustedDate. ” The … Continued

705: invalid-eqd-2-03.xml is valid

The example invalid-eqd-2-03.xml is valid. The example should be invalid. eqd-2 is: ” Context: Trade (complex type) eqd-2 (Mandatory) //equityExercise/equityAmericanExercise/expirationDate/adjustableDate/unadjustedDate must be greater than or equal to tradeHeader/tradeDate. ” The two fields are: 2001-07-13Z 2001-07-13Z

704: invalid-eqd-2-04.xml is valid

The example invalid-eqd-2-04.xml is valid. The example should be invalid. eqd-2 is: ” Context: Trade (complex type) eqd-2 (Mandatory) //equityExercise/equityAmericanExercise/expirationDate/adjustableDate/unadjustedDate must be greater than or equal to tradeHeader/tradeDate. ” The two fields are: 2001-07-13Z 2001-07-13Z

703: invalid-eqd-5-01.xml breaks rule eqd-9

The example invalid-eqd-5-01.xml breaks rule eqd-9. This is a mistake, as it should only break eqd-5. eqd-9 is: ” Context: equityBermudaExercise (complex type) eqd-9 (Mandatory) All dates in bermudaExerciseDates/date must be less than or equal to expirationDate/adjustableDate/unadjustedDate. ” Please fix the example to only break eqd-5.