Latest Posts

The rule states: Context: BrokerEquityOption (complex type) eqd-25 (Mandatory) Preconditions: SameCurrency If numberOfOptions, equityPremium/paymentAmount and equityPremium/pricePerOption are present then: equityPremium/pricePerOption * numberOfOptions = equityPremium/paymentAmount/amount. The rule should state: Context: BrokerEquityOption (complex type) eqd-25 (Mandatory) Preconditions: SameCurrency If numberOfOptions, equityPremium/paymentAmount and equityPremium/pricePerOption are present then: equityPremium/pricePerOption/amount * numberOfOptions = equityPremium/paymentAmount/amount. The difference is the correct version … Continued

The complex type EquitySchedule is not used in the FpML Schema. It remains in fpml-eq-shared, and has a rule around it. fpml-eq-shared.xsd(270):

Context: EquityDerivativeBase (complex type) eqd-23 (Mandatory) equityEffectiveDate >= ../../tradeHeader/tradeDate The correct path to tradeDate is ../tradeHeader/tradeDate

Context: EquityDerivativeBase (complex type) equityEffectiveDate >= ../../tradeHeader/tradeDate The XPath is missing two levels of elements for the equityEffectiveDate. There is the same problem with tradeDate. The XPath required is //element(*, EquityDerivativeBase)/trade/equityOption/equityEffectiveDate And for tradeDate is should be: //element(*, EquityDerivativeBase)/trade/tradeHeader/tradeDate

One of the principles set out by John Weir is that where there is a choice between representing a structure in XSD or as a constraint, it should be preferred to represent it in the XSD. This rule contradicts that AWG principle. Context: CalculationAgent (complex type) eqd-21 (Mandatory) calculationAgentPartyReference must be present.

eqd-20 (Mandatory) Preconditions: SameCurrency If numberOfOptions, optionEntitlement, equityPremium/paymentAmount and equityPremium/pricePerOption are present then: equityPremium/pricePerOption * numberOfOptions * optionEntitlement = equityPremium/paymentAmount/amount. equityPremium/pricePerOption should instead be equityPremium/pricePerOption/amount

EQD-19 states: If notional, equityPremium/percentageOfNotional and equityPremium/paymentAmount are present, then equityPremium/paymentAmount/amount = notional * equityPremium/percentageOfNotional It should state: If notional, equityPremium/percentageOfNotional and equityPremium/paymentAmount are present, then equityPremium/paymentAmount/amount = notional/amount * equityPremium/percentageOfNotional

(see Matthew Rawlings’ feedback on the related http://www.fpml.com/issues/view.php?id=433 issue ) They need to have a valid path in both the SVN structure and in the distribution. We need a valid path in the distribution so we can do development with them. Take valid-bp-1-01.xml as an example. This has the global attribute of xsi:schemaLocation=”http://www.fpml.org/2007/FpML-4-3 ../../fpml-main-4-3.xsd” This … Continued

extension example without extensions: “Also, “eqd_ex01_american_call_stock_long_form.xml” is one of the example files, but doesn’t seem to have any extensions in it.” – tony coates

https://dedicated.fpml.org/viewcvs/branches/ext2/src/schema/Warrant.TradeCreated.xml?rev=2296&view=log This is trivial, but in the example “Warrant.TradeCreated.xml”, I think the currency code is meant to be “AUD” rather than “ASD”. – Tony Coates