This was something I raised to the CUG some time ago in preperation for the new B to B messages. The problem is that for ANY message derived from one of the notification messaging types (novation, payment, trade confirmation, etc.) there is the possibility that one of the parties to the trade will be playing … Continued
The following types should be positiveInteger and not just integer: fpml-asset.xsd(325): fpml-asset.xsd(371): fpml-cd.xsd(639): fpml-cd.xsd(644): fpml-eqd.xsd(433): fpml-eq-shared.xsd(1188): fpml-riskdef.xsd(25): fpml-shared.xsd(611): fpml-shared.xsd(1327):
Party Portfolio name should not contain a party reference, just a name. Either the field is mis-named and mis-documented, or it is mis-modelled. A type to represent a portfolio name for a particular party. A pointer style reference to a party identifier defined elsewhere in the document. The party referenced has allocated the trade identifier.
There are message exchanges in FpML for which the completion is unobservable. It is not apparent to an observer when there will be a follow-up message and when the exchange is completed. For example, for the request quote it is not observable whether the interation completes with the RequestQuoteResponse, or whether there will be a … Continued
Please removed eventId. It duplicates conversationId. It should be removed. There seems to be a rough consensus on this (ex Brian), so please can we discuss at the AWG.
The FpML specification is unclear on the distinction between Transport Level and Business Level messages. For example, it is a generally received understanding, but remains unstated, that you cannot reject a rejectionMessagin. Either we follow 20022 and FIX and treat this as distinct levels: Transport Level and Business Level, or we create some sort of … Continued
Please create an abstract supertype of Leg. All swap legs can extend “Leg”. This would make the model much clearer.
The content is not in alphabetical order. For example “Resource” comes before “Language”.
There are lots of ‘floating’ comments in fpml-cashflow-matching.xsd. These are comments about the schema that are not attached to the item they comment. All comments should be attached. For example the comment should be in the annotation. A message sent to indicate that previously asserted TradeCashFlows are no longer in effect. For example, this may … Continued
Multiple Exercise is not a sub-type of Partial Exercise. Some multiple exercises are full exercise. A type definint multiple exercise. As defining in the 200 ISDA Definitions, Section 12.4. Multiple Exercise, the buyer of the option has the right to exercise all or less than all the unexercised notional amount of the underlying swap on … Continued