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

FpML-BP AWG Teleconference today June 10 at 9am NYC/2pm LON - spreadsheet with message names

As agreed in the previous AWG call, today 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.

Attachment: 5-0 - Messages - Naming patterns.xls
Description: 5-0 - Messages - Naming patterns.xls

--- Begin Message --- 
See updated proposal from Simone Milani-Foglia and comments below.

-----Original Message-----
From: Simone Milani-Foglia [mailto:Simone.Milani-Foglia@xxxxxxxxxxxxxxx]
Sent: Wednesday, June 09, 2010 5:07 AM
To: Marc Gratacos
Cc: Irina Yermakova
Subject: RE: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names

++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please Read The Disclaimer At The Bottom Of This Email
++++++++++++++++++++++++++++++++++++++++++++++++++++++

Hi Marc,

    Thanks for your comments, please see my reply below.  Do you mind forwarding to the whole group (documents and the comments below) as I am having issues sending emails to the mailing list.

Thanks!

Simone

-----Original Message-----
From: Marc Gratacos [mailto:MGratacos@xxxxxxxx]
Sent: 08 June 2010 10:04
To: Simone Milani-Foglia
Subject: RE: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names

Hi Simone,

In terms of the naming, I see some inconsistencies by using Notification and Request in the same name. From my perspective a message is either a request or a notification but not both. -Agreed, my proposal should be consistent with this.

I am also not sure about the value of adding the suffix request, response, etc. in the message name. >>>This is to add clarity and to aid message processing.

In terms of the typing, I agree with you that the suffix Message doesn't add much to the type name.
I am not sure about the value of adding an affirmative and negative response types. It should be clear with the name of the message. >>>This is to have a separate type for messages that will trigger different category of processes: all Negative types are likely to require more attention than Positive types.

Feel free to send this to the whole list.

Thanks,
Marc

________________________________________
From: Simone Milani-Foglia [Simone.Milani-Foglia@xxxxxxxxxxxxxxx]
Sent: Friday, June 04, 2010 12:20 PM
To: Marc Gratacos
Subject: RE: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names

Hi Marc,

    Please find attached my revised proposal.  As much as I could I have followed a pattern were in each name we have one of more attributes followed by a single noun.  I have also updated existing base types.  I suggest changing Request(Response)Message to simply Request(Response)  making it more natural to then use something like ClearingRequest and not ClearingRequestMessage.  I have also added a NegativeResponse and AffirmativeResponse (same for Notification).  Finally I have changed RetractionRequest to RollBackRequest.

I attach the comparison sheet with my new proposal and 3 class diagrams (I have not added the advice type in there, should we add it?).


Your thoughts?

Thanks

Simone

-----Original Message-----
From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: 03 June 2010 09:46
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.

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.

*************************************************************************************************

This email is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient(s) and may only be copied or disclosed with the consent of LCH.Clearnet Limited and/or LCH.Clearnet SA.   If you are not an intended recipient please delete this e-mail and notify postmaster@xxxxxxxxxxxxxxxx
LCH.Clearnet Limited, LCH.Clearnet SA and each other member of the LCH.Clearnet Group accept no liability, including liability for negligence, in respect of any statement in this email.
The contents of this email are subject to contract in all cases, and LCH.Clearnet Limited and/or LCH.Clearnet SA makes no contractual commitment save where confirmed by hard copy.
Cet e-mail et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, est interdite, sauf autorisation expresse de LCH.Clearnet Limited et/ou LCH.Clearnet SA. Si ce message vous a été adressé par erreur, merci de le détruire et d'en avertir immédiatement postmaster@xxxxxxxxxxxxxxxx
LCH.Clearnet Limited, LCH.Clearnet SA et les autres entités du groupe LCH.Clearnet Group, ne peuvent en aucun cas être tenues responsables au titre de ce message à moins qu’il n’ait fait l’objet d’un contrat signé.
LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High Street, London EC3N 1EA.    Recognised as a Clearing House under the Financial Services & Markets Act 2000. Reg in England No.25932
Telephone: +44 20 7426 7000              Internet: http://www.lchclearnet.com
LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, Chambre de Compensation conformément au Code Monétaire et Financier.

*************************************************************************************************


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 (4).xls
Description: 5-0 - Messages - Naming patterns (4).xls

Attachment: ClearingMessageTypes.jpeg
Description: ClearingMessageTypes.jpeg

Attachment: ProposedMessageTypes.jpeg
Description: ProposedMessageTypes.jpeg

Attachment: ExistingMessageTypes.jpeg
Description: ExistingMessageTypes.jpeg


--- End Message ---