That’s a good point Gordon. We propose rescheduling the collateral call an hour earlier to 9am (2pm London) OR an hour later to 11am (4pm London) to accommodate the ISDA Member Call* at 10am that many may want to attend.
What about moving the collateral call to 9am (2pm London)? Let us know ASAP if that works or if you’d prefer another time (9am or 11am or 10am -no change). We’ll move the call to 9am unless there’s strong preference for a different time.
*Note it is an ISDA members only call. ISDA members will have received their invitation already. Also note that call will be recorded and will be made available to the membership base via the ISDA website.
owner-colwg@xxxxxxxx [mailto:owner-colwg@xxxxxxxx] On Behalf Of Peery,
Sent: Tuesday, June 29, 2010 1:32 PM
Subject: FPML-CWG RE: Collateral WG Meeting: Wed June 30, 2010 @ 10am New York / 3pm London
Hi. You may not have as big a crowd because tomorrow ISDA is holding at the same time a "Developments from Washington DC" call ... ideally I'd like to dial into both..
GORDON F. PEERY
State Street Financial Center · One Lincoln Street
Boston, MA 02111-2950
Web site: www.klgates.com
owner-colwg@xxxxxxxx [mailto:owner-colwg@xxxxxxxx] On Behalf Of Lyteck
Sent: Tuesday, June 29, 2010 1:02 PM
Subject: FPML-CWG Collateral WG Meeting: Wed June 30, 2010 @ 10am New York / 3pm London
REMINDER - we'll have a meeting tomorrow Wednesday as usual. We’ll send an updated schema/examples later today.
Next Meeting– Wednesday June 30, 2010 @ 10am New York / 3pm London (1h30)
Going forward, we will use remote web sessions to make it easier to review the schema and examples during the calls. Please note you may need to install a small module to view the meeting. Those who can’t install the module can also follow by opening the XML files directly.
1. Join the web presentation:
Meeting ID: 428-595-714
2. Dial-in details:
US Dial-in: 888-481-3032
UK Toll Free: 0800 904 7961
International Dial-in: 617-801-9600
· FpML 5.1 Working Draft 1 Deliverable (schema, examples, schema documentation, documentation)
· Acknowledge Dispute Notification (MC11), Discuss draft implementation of MC11, the response to the full dispute (MC5) / partial dispute (MC6) (see msg-ex-MC11-acknowledge-dispute.xml)
· Request Portfolio (MC12/MC13) Discuss implementation of MC12/MC13 and the different process options around dispute resolution and portfolio reconciliation. This will help to consider the content of these messages in terms of reconciliation options i.e. unilateral reconciliation with portfolio exchange vs. bilateral reconciliation where there are proactive and reactive scenarios and choice of reconciliation service providers.
Action Items / To do
1. All firms to validate the schema/content model by creating their own XML examples or by providing margin call examples which we can translate to XML.
2. GlobeOp / Richard to put together a list of definitions (i.e., glossary of collateral terms) that will be used to document the schema.
3. Renaming of collateral messages to comply to FpML message naming patterns
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 electronic message contains information from the law firm of K&L Gates LLP. The contents may be privileged and confidential and are intended for the use of the intended addressee(s) only. If you are not an intended addressee, note that any disclosure, copying, distribution, or use of the contents of this message is prohibited. If you have received this e-mail in error, please contact me at gordon.peery@xxxxxxxxxxxx