281: message sequence assumption

The FpML architecture should be specific that there is no assumption that message sequence is preserved over the transport. There is potential for disagreement in implementations over whether message sequence is preserved. In practise no enterprise bus preserves sequence.

280: Coding scheme codes require a maximum length

The length of a code value in an FpML coding scheme is undefined. This needs to be defined for implementations. I propose the code should have a maximum length of 20 chars. There should be a Schematron check on the code values in the build system.

279: Deprecate productType

Please deprecated productType. The information is redundant because it duplicates the productId and the parametric contents of the contract.

278: A text example is represented wrong in the FpML

In the Return Swaps Product Architecture section 9.6.4 example 4, the FpML represents the fxRate in the reverse direction of the word example. The fxRate should be “Currency1PerCurrency2”, which means the amount of currency one for one unit of currency two. The actual text is copied below and states “Currency2PerCurrency1”.

273: Subversion broken

RA layer request failed svn: PROPFIND request failed on ‘/svn/fpml’ svn: PROPFIND of ‘/svn/fpml’: could not connect to server (https://dedicated.fpml.org:8443) I get this message from Subclipse, similar from Tortoise

270: Please clarify if is used within and for SWAP.

Currently it seems may exist for SWAP and SWAPTION trade. My understanding is that : For SWAPTION, early terminations can be done on time as well as date. i.e. The time matters as to when the SWAP can be exercised. Therefore it make sense to have within and . For SWAP (or SWAP within SWAPTION), … Continued