Author: Admin

Publish scheme data as xml files; Scheme URIs should resolve to data files.

A number of the message sequence diagrams in the messaging section that appear in the HTML version of the 4.0 recommendation do not appear in the PDF version. This makes the PDF version much harder to understand. For example, 3.3.1.2 has 1 diagram in the PDF vs. ~10 in the HTML version.

I require support for stubs in Total Return Swaps (aka FpML Equity Swaps). We’re trading TRS with stubs and would like to see stub support, preferably as a small enhancement for 4.1. I would like to see the //swapStream/stubCalculationPeriodAmount element also added to the TRS. In general I would like to see the interest leg … Continued

After discussion with the WG Chair I’ve taken the advice to present as an Issue. For the TradeNotification use case I need to provide the Adjusted Date for a number of fields: Effective, Termination, First Stub, Last Stub. These fields currently have the type ‘AdjustableOrRelativeDate’. This means I can put in an a pre-adjusted adjustable … Continued

This is a comment about how Swap products are assembled from legs inside FpML. FpML Swaps are substitutions of the Product element. Each Swap is made up of different ‘legs’ or ‘swap streams’. Each Swap product use a different composition it’s legs: creditDefaultSwap – feeLeg and protectionTerms fxSwap – fxSingleLeg (repeating) swap – swapStream (repeating) … Continued

I understand the use of the term ‘equity’ to reflect the historical origin of the products defined in fpml-eqs-4-1.xsd. They came out of the equity market as products and the contribution out of an equity team. My most frequent use of ‘equitySwap’ is for Bond Index TRS and LPI TRS. Neither of which could be … Continued

The additionalData element in MessageRejected is of type xs:string, but has no additionalDataType attribute to identify what it is carrying. This is in contrast to the additionalData element inside ReasonCode, which does have such an attribute. We recommend adding the attribute. Since carrying the source document in this field may be quite a common use … Continued

This is a small issue that came out in usage. Within the download the schema is copied 9 times, once in each sub-directory. For those of my colleagues less experienced with FpML this took some explaining. They checked each file and checked they were identical. I can see this may be necessary to get the … Continued

This is my feedback on implementing the TR: Each .xsd file used to be valid independently. They imported everything they needed to be valid by themselves. Within the 4.0 TR this holds for all files except fpml-msg-4-0.xsd. This file has dependencies on types such as ‘Document’ and ‘Trade’ that are defined in fpml-main-4-0.xsd. The circular … Continued

It seems that not enough attention has been paid to designing response messages in the initial draft of 4.0. Outlined below are some changes we would like to see in the standard. We think the message “MessageRejected” is based on the incorrect message type. It is based on NotificationMessage, but this has a header that … Continued