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
I want to know how to make a FpML to definite an embed Options Bond or Convertible Bond. Today, I tried click the linked example(http://www.fpml.org/spec/fpml-5-0-2-wd-2/html/confirmation/xml/bond-options/cb-option.xml) in the confirmation example page. But, unfortunately, the hyperlink is invalid. Also, I did not find any example about embed Options Options in fpml.org. Another question is whether the Convertible … Continued
The rules documentation files are invalid against the XSD. rules-english-ref.xml contains: ” %fpml.version.entities; ]> ” The attribute /rules/@name is not in the XML Schema. There are many other nodes node in the XML Schema. … … Please make the rules documentation valid against the XSD.
Rule 26b needs to have an additional guard: if equityExercise/equityBermudaExercise/equityMultipleExercise/integralMultipleExercise does not exist. Otherwise, it collides with eqd-18. Example: 1 1 150000 150000 —Rules——————— eqd-26b (Mandatory) English Description: Context: EquityOption (complex type) EquityDerivativeShortFormBase (complex type) You cannot exercise more than the number of options you have. If numberOfOptions exists, and if equityExercise/equityBermudaExercise/equityMultipleExercise/maximumNumberOfOptions exists, then equityExercise/equityBermudaExercise/equityMultipleExercise/maximumNumberOfOptions … Continued
Rule 26 needs to have an additional guard: if equityExercise/equityAmericanExercise/equityMultipleExercise/integralMultipleExercise does not exist. Otherwise, it collides with eqd-17. Example: 1 1 150000 150000 — Rules ——————————— eqd-26 (Mandatory) English Description: Context: EquityOption (complex type) EquityDerivativeShortFormBase (complex type) You cannot exercise more than the number of options you have. If numberOfOptions exists, and if equityExercise/equityAmericanExercise/equityMultipleExercise/maximumNumberOfOptions exists, … Continued
” Context: Document (complex type) Every $sellerPartyReference in //sellerPartyReference satisfies $sellerPartyReference/@href eq (trade/tradeSide, party)/@id ” Should be: ” Context: Document (complex type) Every $sellerPartyReference in //sellerPartyReference satisfies $sellerPartyReference/@href eq (trade/tradeSide/@id, party/@id) ” The change is to bring the @id within the brackets. It changes nothing other than bringing it into line with other examples, such … Continued
The XPath version of shared-12 is today: ” XPath 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 XPath version should be: ” Context: for $document in //element(*, Document) every $buyerPartyReference in $document//buyerPartyReference … Continued
The rule shared-10 uses a path that doesn’t exist. There is no element named “CalculationAgent” – that is a type not an element. The rule today: ” shared-10 (Mandatory) Context: CalculationAgent English Description: The values of calculationAgentPartyReference/@href attributes shall be unique. count(distinct-values(calculationAgentPartyReference/@href)) eq count(calculationAgentPartyReference/@href) ” The correct rule, including comment is: ” shared-10 (Mandatory) Context: … Continued
ird-14 handles effectiveDate but not relativeEffectiveDate The rule today is: ” Context: CalculationPeriodDates (complex type) terminationDate/unadjustedDate gt effectiveDate/unadjustedDate ” We can either put a guard on the context to limit the rule to effectiveDate, or we can also evaluate the relativeEffectiveDates With a guard: ” Context: CalculationPeriodDates (complex type)[exists(effectiveDate)] terminationDate/unadjustedDate gt effectiveDate/unadjustedDate ” Handling just … Continued
cd-26 does not handle the effectiveDate being optional. cd-26 today is: ” Context: CreditDefaultSwap (complex type) [exists(feeLeg/singlePayment/adjustablePaymentDate)] feeLeg/singlePayment/adjustablePaymentDate gt generalTerms/effectiveDate/unadjustedDate ” There is a guard on paymentDate, there should also be a guard on effectiveDate. I propose the new rule be: ” Context: CreditDefaultSwap (complex type) [exists(feeLeg/singlePayment/adjustablePaymentDate)][exists(generalTerms/effectiveDate)] feeLeg/singlePayment/adjustablePaymentDate gt generalTerms/effectiveDate/unadjustedDate ” I do not know … Continued