Latest Posts

Remove types deprecated in FpML-4 from FpML-5

Caused by complex type BasicQuotation The base type which all FpML products extend. Per R. Stowsky proposal for pre-trade. TODO: This will require migrating BasicQuotation into shared to eliminate the dependency errors.

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: fixedRateSchedule ird-51 (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: notionalStepSchedule ird-50 (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: businessCentersReference ird-26 (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: stubCalculationPeriodAmount ird-23 (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: calculationPeriodDates ird-10 (Mandatory) … Continued

Section 4.6.1 states: “The context of the rule must be defined such that incorporates everything referred to in a rule. The rule must not use the ancestor or parent axis, or use them in cojunction with any other axis. For example “../../tradeHeader” is precluded.” This contradicts: Context: knownAmountSchedule ird-54 (Mandatory) Preconditions: isParametric The dates in … Continued

Section 4.6.1 states: “The context of the rule must be defined such that incorporates everything referred to in a rule. The rule must not use the ancestor or parent axis, or use them in cojunction with any other axis. For example “../../tradeHeader” is precluded.” This contradicts: Context: floorRateSchedule ird-53 (Mandatory) Preconditions: isParametric The dates in … Continued

Section 4.6.1 states: “The context of the rule must be defined such that incorporates everything referred to in a rule. The rule must not use the ancestor or parent axis, or use them in cojunction with any other axis. For example “../../tradeHeader” is precluded.” This contradicts: Context: capRateSchedule ird-52 (Mandatory) Preconditions: isParametric The dates in … Continued