Latest Posts

792: ln-19 should refer to exists() as a function

By

The current ln-19: ” ln-19 (Mandatory) Context: DrawdownNotice (complex type) [drawdownEventType = RateSetEvent] [exists(loanContract)] loanContract/currentInterestRatePeriod/interestRate and loanContract/currentInterestRatePeriod/margin and loanContract/currentInterestRatePeriod/allInRate and loanContract/currentInterestRatePeriod/interestDayBasis and loanContract/currentInterestRatePeriod/indexTenor must exist. ” As written this is the XPath “and” of the contents of an element with another. This isn’t what is meant in the rule. “exists()” should be used as a … Continued

789: invalid-ln-16-01.xml is invalid against ln-13

By

The sample file invalid-ln-16-01.xml is invalid against ln-13. According to the FpML Manual each sample must be invalid against only the one rule it tests, in this case ln-13. Please correct invalid-ln-16-01 so it is valid against ln-13.

788: ln-16 cannot compare two money types

By

ln-16 tries to get the typed value of two elements with element only content. i.e. the elements contain other elements so you cannot compare them other than as sets, which is presumably not what is meant. The rule today is: ” ln-16 (Mandatory) Context: DrawdownNotice (complex type) [exists(facilityCommitmentPosition/priorAmount/shareAmount)] [same-currency((facilityCommitmentPosition/priorAmount/shareAmount,drawdownPayment/shareLoanContractAmount))] drawdownPayment/shareLoanContractAmount

787: invalid-ln-14 is invalid against ln-13

By

The sample invalid-ln-14 is invalid against ln-13. According to the FpML Manual it must only be invalid against the one rule it tests. Please fix the sample so that it is only invalid against ln-13.

786: ln-15 has undefined precedence

By

ln-15 has undefined precedence for the different clauses. The rule today is: ” ln-15 (Mandatory) Context: DrawdownNotice (complex type) [exists(dealIdentifier/creditAgreementDate)] loanContract/effectiveDate and drawdownPayment/paymentDate >= dealIdentifier/creditAgreementDate. ” “loanContract/effectiveDate and drawdownPayment/paymentDate” returns in XPath true if both elements exist. “drawdownPayment/paymentDate >= dealIdentifier/creditAgreementDate” returns true if an element in the first path occurs in the second. What is … Continued

785: invalid-ln-11-02.xml not triggered by ln-12

By

The invalid example invalid-ln-12-01.xml is not triggered by ln-12. The rule today is: ” ln-12 (Mandatory) Context: FacilityNotice (complex type) [facilityCommitmentPosition/loanContractPosition exists] [same-currency((facilityCommitmentPosition/priorAmount/shareAmount/amount,//facilityCommitmentPosition/loanContractPosition/priorAmount/shareAmount/amount)) = True] facilityCommitmentPosition/priorAmount/shareAmount/amount >= the sum of all facilityCommitmentPosition/loanContractPosition/priorAmount/shareAmount/amount. ” The example does not contain an element of type FacilityNotice. Please fix the example or rule as appropriate.

784: invalid-ln-11-01.xml not triggered by ln-11

By

The invalid example invalid-ln-11-01.xml is not triggered by ln-11. The rule today is: ” ln-11 (Mandatory) Context: FacilityNotice (complex type) [facilityCommitmentPosition/loanContractPosition exists] [same-currency((facilityCommitmentPosition/currentAmount/shareAmount/amount,//facilityCommitmentPosition/loanContractPosition/currentAmount/shareAmount/amount)) = True] facilityCommitmentPosition/currentAmount/shareAmount/amount >= the sum of all facilityCommitmentPosition/loanContractPosition/currentAmount/shareAmount/amount. ” The example does not contain an element of type FacilityNotice. Please fix the example or rule as appropriate.