871: cd-6 is invalid XPath

cd-6 today: ” cd-6 (Mandatory) Context: GeneralTerms Formal Description: buyerPartyReference/@href neq sellerPartyReference/@href ” corrected: ” cd-6 (Mandatory) Context: GeneralTerms Formal Description: buyerPartyReference/@href ne sellerPartyReference/@href “

870: cd-14 precise description should be in XPath and be less wordy

cd-14 today is: ” The @href attribute of protectionTerms/creditEvents/creditEventNotice/notifyingParty/sellerPartyReference eq the @href attribute of generalTerms/sellerPartyReference ” the correct precise description is: ” protectionTerms/creditEvents/creditEventNotice/notifyingParty/sellerPartyReference/@href eq generalTerms/sellerPartyReference/@href “

869: guard on cd-15 needs to use “eq” instead of “=”

The guard on cd-15 needs to change in the precise description: currently: ” [count(generalTerms/referenceInformation/referenceObligation)=1] [exists(cashSettlementTerms/valuationDate/singleValuationDate)] ” fixed: ” [count(generalTerms/referenceInformation/referenceObligation) eq 1] [exists(cashSettlementTerms/valuationDate/singleValuationDate)] “

868: guard on cd-17 needs to use eq instead of =

The guard on cd-17 in the precise description is: ” [count(generalTerms/referenceInformation/referenceObligation)=1] [exists(cashSettlementTerms/valuationDate/multipleValuationDates)] ” It should be: ” [count(generalTerms/referenceInformation/referenceObligation) eq 1] [exists(cashSettlementTerms/valuationDate/multipleValuationDates)] “

867: declare functx namespace

The functx namespace needs declaring in the Validation Rules. functx is the namespace for a standard function library in XPath. The functx namespace is used in some IRD rules. The namespace should be defined just like the other namespaces. Add this to the namespace declaration in the rules: ” namespace functx = http://www.functx.com “

866: New HTML layout doesn’t match the agrement document

The new HTML layout is largely fine, but has some problems where it doesn’t match the spirit or letter of what was agreed. Problem #1 The first problem is the guard on the context is given in the body of the rule and not the context. This disassociated the guard from the context and also … Continued

865: New value required in businessCenter coding scheme for Brazil Business Day to support BRL CDI Non-Deliverable IR Swaps

Per the EMTA/ISDA Market Practice statement Recommended EMTA-ISDA Market Practice for BRL CDI Non-Deliverable Interest Rate Swap Transactions published at http://www.isda.org/publications/pdf/SwapsCDsMP1.pdf the definition of a Brazil Business Day is very specific and defined as follows: Brazil Business Day means a business day in any of Sao Paulo, Rio de Janeiro or Brasilia not otherwise declared … Continued

863: Precondition ‘isParametric’ on IRD rules is bogus

The precondition ‘isParametric’ is attached to the majority of the IRD rules. The precondition is satisfied (true) where InterestRateStream/cashflows is absent (“does not exist”), or cashflows/cashflowsMatchParameters is true; in other words (informally) in all cases where not(cashflowsMatchParameters is false). The purpose of cashflowsMatchParameters is to declare whether (or not) the content of cashflows (multiple paymentCalculationPeriods, … Continued

862: Knock complex type should force at least one of knockIn or knockOut

The design of the Knock type and its usage with an optional element of the OptionFeatures type means that it is possible to define an equityOption or equityOptionTransactionSupplement that contains a knock feature but omits any definition of the knock in/out levels. e.g. … … … … I suggest that the model for Knock type … Continued