I’d like to use fpML for event notification. Please extend fpML to support event notification for: 1) Reset Payment Notifications. 2) Collateral Payment Notification. 3) Re-fix notifications. 4) Rate Reset Notification. 5) Termination instruction. 6) Rollover instruction. The scenario I have is informing an external securities service provider (fund administrator) of these events. We anticipate … Continued
This is an enhancement request. The current “party” structure requires enhancing to support non-BIC identifiers and to support accounts. In my typical scenario a fund manager is a party that trades on behalf of a client. The client is the party that the trade should be booked to. In addition we’d need to handle multiple … Continued
FpML uses a deficient identification scheme for ISO currency codes – the URI does not mention which version of the ISO 4217 standard is being used. This means that the example trades containing pre-euro currencies such as DEM are valid prior to the Euro conversion, but invalid after, because ISO 4217 no longer contains these … Continued
The PDF documentation for the rateTreatmentScheme coding scheme values is incorrect. The PDF documentation incorrectly uses the definition from the negativeInterestRateScheme. The correct documentation for these codes is in the MS Word documentation for FpML 2.
The callPutSchemeDefault element on the FpML root element is declared but never used. Inconsistent naming of scheme: exchangeIdScheme/exchangeIdTypeSchemeDefault Suggest drop the “Type” text out of the attribute name exchangeIdTypeSchemeDefault Missing scheme default attribute on the FpML/root element for: instrumentIdScheme used on the instrumentId element. Suggest adding instrumentIdSchemeDefault attribute on FpML/root element. Inconsistent naming of masterAgreementTypeScheme … Continued
I wonder if it would be possible to introduce some consistency between the URI naming convention for new and old parts of FpML, e.g. – the URI for payerReceiverScheme is http://www.fpml.org/spec/2001/payer-receiver-1-0 while: – the URI for touchConditionScheme is http://www.fpml.org/spec/2002/touch-condition-scheme-1-0 i.e. newer URI’s append the word “scheme”. This will assist vendors who actually use these URI’s … Continued
In section 7 of the April 17 WD of FpML 3.0, there was a proposed change to the use of scheme defaults: Here is the text of the proposal: Quote: “The FpML Working Groups are considering removing the scheme default attributes from the FpML root element and changing the scheme attributes from being #IMPLIED to … Continued
At the last Standards Committee meeting there was alot of feedback of implementations of FpML 2.0. As a result it being proposed to move FpML 2.0 to Recommendation. Are there any objections from anyone in this group to such a move ? If so please state the reasons why we should not move to Recommendation. … Continued