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.
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
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.
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
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.
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.
ln-10 refers to the element facilityIdentifier. This element does not exist anywhere in FpML. Please correct ln-10. The rule today: ” ln-10 (Mandatory) Context: FacilityNotice (complex type) [facilityIdentifier/originalCommitmentAmount exists] [facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount exists] [same-currency((facilityIdentifier/originalCommitmentAmount,facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount)) = True] facilityIdentifier/originalCommitmentAmount/amount >= facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount/amount. “
FpML include paths in most of the cases are indirect. For example, “fpml-fx.xsd” uses enumerated types such as PayoutEnum, but does not directly include the file “fpml-enum.xsd”, where enumerated types are defined This is Legal in XML Schema 1.0, but illegal in XML Schema 1.1 Tools should support XML Schema 1.0 fully, but unfortunately not … Continued
The FX schema must use the currency type in fpml-shared for currencies. This is affecting validation rules. The type of /FpML/trade/fxSingleLeg/exchangeRate/quotedCurrencyPair/currency1 is xs:normalizedString. This is wrong. Either this should be an IDREF within the document to refer to a currency ID or it should be of type “Currency”. Currency is defined in fpml-shared as: ” … Continued
The Validation Rules use the xs namespace but it is not defined. Add the definition of xs namespace to each page’s namespace definition. ln-8 is an example of using the xs namespace: ” ln-8 (Mandatory) Context: InterestAccrualSchedule (complex type)[MultipleLenderLoanContractPeriod(.)] Rule: every $startDate in $interestAccrualSchedule/lenderLoanContractPeriod[startDate > min($interestAccrualSchedule/lenderLoanContractPeriod/startDate)]/startDate satisfies $startDate – xs:dayTimeDuration(“P1D”) = $interestAccrualSchedule/lenderLoanContractPeriod/endDate Comment: Each lendLoandContractPeriod … Continued