FpML Issues Tracker
The type BrokerConfirmation is weakly defined:
1. The element has one mandatory child element. What data does this element convey that its children don't? Can it be flattened? 2. The definition is rhetorical. It needs more flesh. 3. brokerConfirmationType is a type - the word type is redundant and should be removed.
03/07/07 11:58 am
This is a confirmation message sent from the executing broker to the parties to the execution
The model appears wrong, it is both weakly defined, and incorrectly located
JPM supports this ( AJ, AP, MR, HMcA )
11/21/07 2:59 pm
CDWG: participants (DTCC and T-Zero) think that it’s not worth doing these changes.
11/21/07 3:01 pm
There are some architectural about naming and containers that should be tackled by the Modelling Task Force.
11/27/07 5:13 pm
Suggestion from Ben: Identifies the market sector in which the trade has been arranged.
12/07/07 9:08 am
Documentation of the complex type has been updated in the 4.3 (4.3 branch) and 4.4 (trunk).
Leave an update
You must be logged in to post an update.