AbandonOrder Advertisement AllocationAlleged AllocationAlreadyMatched AllocationAlreadySubmitted AllocationConfirmed AllocationMatched AllocationMismatched AllocationUnmatched AllocationAmendmentConfirmed CancelAllocationConfirmation ConfirmAllocation AllocationConfirmationCancelled OrderFilled OrderWithdrawn FullyAllocated IndicationOfInterest ModifyAllocationMatch Order WithdrawIndicationOfInterest WithdrawOrder
Review content model The whole allocation process, the content model, the use of contracts. It all needs review.
I have 4 separate ISDA passwords, merge them into one username/password combination. 1. ISDA Ops website 2. FpML Specifications 3. FpML Issue list 4. FpML Subversion
It should be reflected in the model.
Version Identification has been incorporated into FpML (choice between tradeId and versionedTradeId). Guidelines on how to use versioning are needed.
-AmendmentConfirmed- not sure when it should be sent. -No response for RequestAmendmentConfirmation. Shouldn’t AmendmentConfirmed be a response message? -Failure/successes are missing. -At what point do we send the RequestAmendmentConfirmation? What’s the condition that triggers it? If you are just confirming a later version of the trade, do we really need this message pattern?
-TerminationConfirmed- not sure when it should be sent. -No response for RequestTerminationConfirmation. Shouldn’t TerminationConfirmed be a response message? -Failure/successes are missing. -At what point do we send the RequestTerminationConfirmation? What’s the condition that triggers it? If you are just confirming a later version of the trade, do we really need this message pattern?
Messages for expiration and rejection are missing. TradeCashflowsAsserted message should be a request message.
The schema annotation of otherRemainingParty (Novation type) is not available in the html documentation.
The html specification doesn’t include the messages for trade status enquiry, which are available in the schema.