Apologies. I also have a conflict.
From: owner-colwg@xxxxxxxx <owner-colwg@xxxxxxxx>
To: colwg@xxxxxxxx <colwg@xxxxxxxx>
Sent: Wed Jul 28 09:21:48 2010
Subject: FPML-CWG Collateral WG Meeting Today: Wed July 28, 2010 @ 10am New York / 3pm London
We’ll have a meeting today as planned to review and sign-off on the collateral documentation and deliverables for publication in FpML version 5.1 (1st working draft). We will discuss the word document. The zip file has not changed. Sorry for the late invite.
Next Meeting Today – Wednesday July 28, 2010 @ 10am New York / 3pm London
1. Please join my meeting.
Meeting ID: 151-660-907
2. Join the conference call:
US Dial-in: 888-481-3032
UK Toll Free: 0800 904 7961
International Dial-in: 617-801-9600
Could we use the meeting time today to go over the documentation together and to discuss a couple of gaps/issues I noticed while going through the documentation? Here is my draft of the documentation to date.
This email and any files transmitted with it are confidential and proprietary to Algorithmics Incorporated and its affiliates ("Algorithmics"). If received in error, use is prohibited. Please destroy, and notify sender. Sender does not waive confidentiality or privilege. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. Algorithmics does not accept liability for any errors or omissions. Any commitment intended to bind Algorithmics must be reduced to writing and signed by an authorized signatory.
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.