Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: calculationAgent shared-10 (Mandatory) … Continued
Samples in trunk are still FpML-4-4
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: payerPartyReference shared-5 (Mandatory) … Continued
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: resetDates ird-59 (Mandatory) … Continued
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: paymentDates ird-55 (Mandatory) … Continued
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: knownAmountSchedule ird-54 (Mandatory) … Continued
Currently refers to FpML-4-4 Working Draft 2007-12-24
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: floorRateSchedule ird-53 (Mandatory) … Continued
Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: capRateSchedule ird-52 (Mandatory) … Continued
Currently refers to FpML-4-4