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: fixedRateSchedule ird-51 (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: FirstPeriodStartDate (complex type) ref-5 (Mandatory) The @href attribute … 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: payerPartyReference shared-5 (Mandatory) If ../receiverPartyReference exists, then the … 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: notionalStepSchedule ird-50 (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: eqd-12 (Mandatory) expirationDate/adjustableDate/unadjustedDate must be greater than or equal … 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: eqd-5 (Mandatory) expirationDate/adjustableDate/unadjustedDate must be greater than or equal … 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: eqd-4 (Mandatory) commencementDate/adjustableDate/unadjustedDate must be greater than or equal … 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: eqd-2 (Mandatory) expirationDate/adjustableDate/unadjustedDate must be greater than or equal … 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: eqd-1 (Mandatory) commencementDate/adjustableDate/unadjustedDate must be equal to ../../../tradeHeader/tradeDate.
Rules shared-5 requires that the payerPartyReference and receiverPartyReference be disjoint. This is to ensure the payer and receiver are disjoint. The problem is this rule falsely assumes that any two parties are always disjoint. There is nothing in the schema or Architecture to require two parties to be disjoint. In practise I am seeing messages … Continued