The root page of the HTML documentation has a cryptic name. You need to navigate to tr-fpml-4-2-2006-05-08/html/fpml-4-2-intro-frame.html Rather than the catchy “fpml-4-2-intro-frame.html”, please could it be called “index.html” which is a web convention for the main page. It would make life so much easier. Optionally, you could also add a readme conveying this information
For support of long form CDS transactions in FpML an additional code value of “ISDA2003CreditArgentineRepublic” should be added to the contractualSupplementScheme. The description should be “Additional Provisions for the Argentine Republic: Excluded Obligations and Excluded Deliverable Obligations dated December 21, 2005.”. These additional provisions were published by ISDA and are available at www.isda.org under Bookstore/Publications->ISDA … Continued
The date display format used in Issues Tracker (e.g. Date Submitted, Last Update) is ambiguous. Date/times are displayed in the form “MM-DD-YY hh:mm” – so a date like “05-06-07” has (at least) three possible interpretations depending on the cultural background and locale of the reader. I suggest we adopt the ISO 8601 international standard notation … Continued
I found out that the FpML specs are a bit ambiguous with respect to the definition of country codes and countryScheme. From: http://www.fpml.org/spec/2006/tr-fpml-4-2-2006-05-08/html/fpml-4-2-schemes-frame.html URI: http://www.fpml.org/ext/iso3166 A valid 2 character country code as defined by the ISO standard 3166 – Codes for representation of countries http://www.niso.org/standards/resources/3166.html. It really should be “ISO 3166-1 alpha-2”. ISO 3166 is … Continued
Does FpML provide means for sending an event for option exercise, knock-in, expiration?
I don’t recall when, but I remeber this happening once in the past as well. The enumeration types are all being generated incorrectly in the documentation. For example see: http://www.fpml.org/spec/2006/tr-fpml-4-2-2006-05-08/html/fpml-enum-4-2.html#Simple_CalculationAgentPartyEnum The table header is supposed to be Value / Source / Description. and then each line should have the element name / FpML / annotation. … Continued
We recently started trading ABX CDS’s which we message over to our accounting agent via FpML. They are telling us that the trades get rejected from their systems because of the following: ****************************************************************************** Following are the business validation rules that failed: ****************************************************************************** Rule number=CDS_Rule1 Error description=Trade date is not before Unadjusted Effectivedate. However, ABX CDS … Continued
In section 3.4.2 of the documentation, Error Handling, the message interaction is described using a message of type “AnyMessage”. To be correct, this should be renamed as “Message”. Any type that implements Message (therefore including its derived messages), would then be legal. AnyMessage is the a description of the message and not its type.
Please add a message rejected example to the example XML documents in FpML. An example has been attached.
Could someone advise me on the following: I need an ability to model CreditDefaultSwap as a quotable product for the negoitiation process. Is there any way to do it aside from customizing the FpML schema? Please advise, your help is greatly appreciated! -Vera