As promised at today's call, I have updated the sheet to show the message names generated using a formula encoding a message naming pattern, to make it clearer how the message names are generated using each proposal. I have added three tabs at the front. - the first is the current 5.0 LCWD naming convention - the second is the LCH/PS proposal - the third is the revision to the LCH proposal that I suggested in the call In each case I have shown the pattern in the first row of each section, with a light blue background, and using the "XXX" process name. This approach makes it easier to see how the message names are constructed, but a bit harder to compare the various patterns. I've left Irina's sheet, which does that better, renamed it to SideBySideComparison, and added a column for the LCH/BAL proposal. -----Original Message----- From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx] On Behalf Of Marc Gratacos Sent: Thursday, June 03, 2010 4:46 AM To: awg@xxxxxxxx Cc: bpwg@xxxxxxxx Subject: FpML-BP FW: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names Importance: High See attached proposal from Irina (.xlsx) ________________________________________ From: Irina Yermakova Sent: Wednesday, June 02, 2010 6:54 PM To: Marc Gratacos Subject: FW: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names Marc, I attached updated 5-0-Messages-Naming patterns.xlsx with my messages naming proposal. Basically, I agree that the 5-0 messages naming needs to be corrected, but I against the first proposal only because it does not go far enough and creates more ambiguity in the naming of the message processes. Let me know your thoughts about my proposal. P.S. I added 3 comments as well (look for red triangle) could you review them too? It looks that two messages that are currently notifications needs to be a response instead. Thank you, Irina -----Original Message----- From: owner-awg@xxxxxxxx [mailto:owner-awg@xxxxxxxx] On Behalf Of Marc Gratacos Sent: Monday, May 31, 2010 6:25 AM To: awg@xxxxxxxx Cc: bpwg@xxxxxxxx Subject: FpML-AWG AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names Importance: High As agreed in the previous AWG call, next Thursday will continue the discussion around the FpML 5.0 messaging issue reported by LCH.Clearnet. See attached a spreadsheet with the list of messages and their names with the current and proposed patterns. Please propose alternative patterns if you want. Members of the BPWG interested in this issue please join the call. US: 888 481 3032 Intl: 617 801 9600 UK: 0800 904 7961 Participant Code: 8682747 Agenda. 1. Message Naming Issue 2. AOB Thanks, Marc 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 <mailto: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. 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 <mailto: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.
Attachment:
5-0 - Messages - Naming patterns.xls
Description: MS-Excel spreadsheet