Please merge the ext2 branch into the trunk. I assume they will continue to be packaged and distributed separately. At the moment it is time consuming to keep them in synch. NB This doesn’t mean the ext2 branch will be released, it just means extensions will be kept properly in synch – they will be … Continued
eqd-18 (Mandatory) If equityExercise/equityBermudanExercise/equityMultipleExercise is present, and numberOfOptions is present then: maximumNumberOfOptions * integralMultipleExercise (in equityExercise/equityBermudanExercise/equityMultipleExercise) is less than or equal to numberOfOptions. The correct XPath contains Bermuda (without the trailing “n”). equityExercise/equityBermudaExercise/equityMultipleExercise
eqd-17 says: “If equityExercise/equityAmericanExercise/equityMultipleExercise is present, and numberOfOptions is present then: maximumNumberOfOptions * integralMultipleExercise (in equityExercise/equityAmericanExercise/equityMultipleExercise) is less than or equal to numberOfOptions.” The problem with this is that maximumNumberOfOptions is also in equityExercise/equityAmericanExercise/equityMultipleExercise, but the rule does not state this. If you follow it literally you are trying to find maximumNumberOfOptions on the context … Continued
/FpML/trade/equityOption/equityExercise/equityAmericanExercise/equityMultipleExercise/minimumNumberOfOptions Add an explanation that these can be fractional amounts.
Add a facet of a minimum number to /FpML/trade/equityOption/equityExercise/equityAmericanExercise/equityMultipleExercise/minimumNumberOfOptions
Context: EquityExercise (complex type) eqd-15 (Mandatory) If equityValuation/equityValuationDate/adjustableDate exists, and equityEuropeanExercise exists, then equityValuation/equityValuationDate/adjustableDate/unadjustedDate must be equal to equityEuropeanExercise/expirationDate/adjustableDate/unadjustedDate. The path does not exist: “//element(*, fpml:EquityExerciseValuationSettlement)[equityValuation/equityValuationDate/adjustableDate]” The correct path should be: “//element(*, fpml:EquityExerciseValuationSettlement)[equityValuation/valuationDate/adjustableDate]” “equityValuationDate” should be “valuationDate”.
The context given for eqd-15 is “Context: EquityExercise (complex type)” There is no type with this name in FpML. I expect the correct type is EquityExerciseValuationSettlement. The rule needs correcting.
This issue was resolved with the outcome that, as of the last two published drafts, all dates in the FpML examples now carry an explicit timezone offset expressed as “-00:00”. If we insist that all samples should include the timezone, then we should use the canonical ‘Z’ form (e.g. 2007-08-15Z), which has the merit of … Continued
Please add the name fpml to the fpml namespace declaration in the validation examples. This makes testing and development much easier. … version=”4-3″ xmlns=”http://www.fpml.org/2007/FpML-4-3″ xmlns:fpml=”http://www.fpml.org/2007/FpML-4-3″ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”http://www.fpml.org/2007/FpML-4-3 fpml-main-4-3.xsd http://www.w3.org/2000/09/xmldsig# xmldsig-core-schema.xsd” xsi:type=”RequestTradeConfirmation” … It is the line xmlns:fpml=”http://www.fpml.org/2007/FpML-4-3″ that needs adding to the examples
There is no eqd-11 rule. Please renumber the rules accordingly to fill the gap.