[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: MTF - Message Classification v1.00



Title: FW: MTF - Message Classification v1.00

Apologies, but I will not be able to make the meeting.

 

From: mtf@xxxxxxxx [mailto:mtf@xxxxxxxx] On Behalf Of Brian Lynn
Sent: Friday, April 25, 2008 7:43 AM
To: mtf@xxxxxxxx
Subject: FW: MTF - Message Classification v1.00

 

For discussion at today’s MTF meeting.

 

From: Lyteck Lynhiavu [mailto:LLynhiavu@xxxxxxxx]
Sent: Thursday, April 24, 2008 10:05 PM
To: brian.lynn@xxxxxxxxxxxxxxxxxxx
Subject: MTF - Message Classification v1.00

 

Brian:

 

Please find attached:

1.      a new version of the Messaging Object Model PDF (updated to 4.4 LCWD)

2.      a classification of FpML Messages (Excel) grouped by the business process associated with the post trade event (instead of grouping by the type of business event (as shown in the PDF). It incorporates most your suggestions.

o    (Both files are complementary and color coding is in sync wherever possible.)

Please forward to the MTF, if alright. I can make further corrections before the meeting, if necessary.

Thanks, Lyteck

-----Original Message-----
From: Brian Lynn [mailto:brian.lynn@xxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 23, 2008 9:35 AM
To: Lyteck Lynhiavu
Subject: RE: MTF - Message Classification v1.00

I've added a column with my suggestions, for your consideration.

I also suggest that you add a column with the current subschema file that each message is located in.  I think that it should be similar to (but not identical) to my suggestions - it would be interesting to see the discrepancies.

For the response messages, it would be interesting to add a column to distinguish between processing failure type messages (TradeNotFound, TradeAlreadySubmitted, etc.) and results (e.g. TradeMatched, TradeMismatched).  We agreed to consolidate the first type, but not the second.

[...]

- Brian

-----Original Message-----
From: Brian Lynn [mailto:brian.lynn@xxxxxxxxxxxxxxxxxxx]
Sent: Monday, April 21, 2008 4:34 PM
To: Lyteck Lynhiavu
Subject: RE: MTF - Message Classification v1.00

Instead of grouping the messages by the type of business event, they should be grouped by the business process associated with the post trade event.

So, for example, under confirmation we would have messages for confirming each of the different types of post trade event.  Similarly for notification.

I think we will end up with business processes something like

- pretrade/RFQ
- trade execution
- confirmation
- notification
- consent negotiation
- reporting, portfolio recon
- cash flow matching

-----Original Message-----
From: mtf@xxxxxxxx [mailto:mtf@xxxxxxxx] On Behalf Of Brian Lynn
Sent: Friday, April 18, 2008 1:57 PM
To: mtf@xxxxxxxx
Subject: MTF minutes April 18, 200WG

Implementation of vote on messaging
===================================
[...]

For the message consolidations, we agreed to produce a summary of messages by business process and type (request, response, etc.) and use this a basis for recommending the messages to be consolidated.  Lyteck will develop a spreadsheet to summarize this, based in part on the PDF of messages he circulated today.  However, we need to group similar processes on different event types (e.g. notification vs. confirmation of post-trade events).

************************************************************************************************************************** The information contained in either this email and, if applicable, the attachment, are confidential and are intended only for the recipient. The contents of either the email or the attachment may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, or distribution is prohibited and may be unlawful. If you have received this communication in error, please notify us by e-mail at isda@xxxxxxxx then delete the e-mail and all attachments and any copies thereof. This communication is part of an ISDA process and is not intended for unauthorized use or distribution. **************************************************************************************************************************