Latest Posts

Please add the following as a comment for eqd-2: “When traded, a contactual option expiry date must be after the trade date.”

I propose we introduce the principle that each rule must have a single context. If a rule currently has multiple contexts then it must be split into multiple rules. If a rule has multiple contexts, then it is merely coincidence that it works across both structures. If it works across multiple contexts because of a … Continued

The Credit Derivatives “Conditions” are derived values added to new Nodes (elements and attributes) defined by the condition. For example: ” Condition: ISDA1999Credit (context: Trade) (context: Contract) At least one of documentation/contractualDefinition element and documentation/masterConfirmation/masterConfirmationType element exists and contains the string “ISDA1999Credit”. Formal description: some $document in (//element(*, Trade) | //element(*, Contract))/documentation/(contractualDefinitions | masterConfirmation/masterConfirmationType) satisfies … Continued

We should complete the current partial conversion of the XPath contexts to XPath. eqd-4 is a good example: ” XPath Description: Context: //element(*, Trade) (complex type) [exists(equityOption/equityExercise/equityAmericanExercise)] equityOption/equityExercise/equityAmericanExercise/expirationDate/adjustableDate/unadjustedDate ge tradeHeader/tradeDate ” The context doesn’t need to have “(complex type)” after it, because in XPath it is clear this is a complex type. “complex type” was … Continued

The English version of shared-12 is: ” shared-12 (Mandatory) English Description: Context: Document (complex type) For buyerPartyReference anywhere in the document, @href shall match the @id attribute of a party element or the @id attribute of a tradeSide element. ” The phrase “anywhere in the document” is ambiguous because “document” is not defined. Does it … Continued

Please apply this patch to remove ref-6 from the XQuery implementation. It has already been removed from the rules. Index: fpml-ref.xq =================================================================== — fpml-ref.xq (revision 6045) +++ fpml-ref.xq (working copy) @@ -26,9 +26,6 @@ for $settlementTermsReference as element(*, SettlementTermsReference) in //element(*, SettlementTermsReference) return res:pretty-result(xs:NMTOKEN(“ref-4”), id($settlementTermsReference/@href) instance of element(*, SettlementTerms), $settlementTermsReference, ()) , -for $interestCalculationReference as … Continued

ISDA is in the process of publishing Supplement number 14 to the 2006 ISDA Definitions. A draft is published at http://www.magnetmail.net/images/clients/ISDA/attach/SUPP14DayCountFractionandminoramendmentFINALCLEAN060109.doc This supplement includes the addition of a new day count fraction “Act/365L”. A new Day Count Fraction coding scheme value is required as a result. The FpML code value should be “ACT/365L” and the … Continued

The rule cd-9 does not cope with multiple referenceObligation within its context. The rules today: ” English Description: Context: ReferenceInformation (complex type) If referenceObligation/primaryObligorReference exists, then the attribute @href of referenceObligation/primaryObligorReference must be equal to the @id attribute of referenceEntity XPath Description: Context: ReferenceInformation (complex type) [exists(referenceObligation/primaryObligorReference)] The attribute @href of referenceObligation/primaryObligorReference eq the @id … Continued

cd-6 is incorrect. The context should be indicated as a Complex Type. Currently, the context is given as an element. Today: ” XPath Description: Context: GeneralTerms buyerPartyReference/@href ne sellerPartyReference/@href ” Correct: ” XPath Description: Context: GeneralTerms (complex type) buyerPartyReference/@href ne sellerPartyReference/@href ” element(GeneralTerms) – today in XPath element(*, GeneralTerms) – correct in XPath

cd-2 changed in revision 5360. It now says: ” Context: Trade (complex type) [exists(calculationAgent)] child::calculationAgent = (calculationAgentPartyReference, calculationAgentParty eq “AsSpecifiedInMasterAgreement”) ” 1. The form “child::” is redundant. 2. There may be more than one calculationAgent. What it should say is instead is what is in the XQuery implementation: ” Context: Trade (complex type) [exists(calculationAgent)] every … Continued