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

RE: FPML-CWG Collateral WG Meeting: Wed June 30, 2010 @ 10am New York / 3pm London



Hi Lyteck,

I have a conflict and will not be able to attend.

 

Best Regards…Tom

 

Thomas L. Brown Jr. | Senior Manager

Standards & Market Practice

Omgeo LLC
55 Thomson Place, Boston, MA  02210
Tel: +1 617 856 2682

Cell: 617 283 5200  
Email: tom
.brown@xxxxxxxxx

Omgeo.  All together now.  www.omgeo.com
A DTCC | Thomson Reuters Company

This e-mail and any attachments may contain proprietary, confidential or privileged information.  If you are not the intended recipient of this e-mail, you must not review, disclose, copy, retransmit or use it.  Please notify us immediately by return e-mail if you have received this e‑mail in error and delete this e-mail and destroy all copies of it and any attachments.

 


From: owner-colwg@xxxxxxxx [mailto:owner-colwg@xxxxxxxx] On Behalf Of Lyteck Lynhiavu
Sent: Tuesday, June 29, 2010 1:02 PM
To: 'colwg@xxxxxxxx'
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:

https://www2.gotomeeting.com/join/428595714

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

Passcode:                            8682747

  

Agenda

·         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)

<disputeAcknowledgement …>

                …

                <variationMargin>
                               
<disputedAmount>
                                               
<currency>USD</currency>
                                               
<amount>200000</amount>
                               
</disputedAmount>
                               
<disputeDate>2010-06-30</disputeDate>
                               
<disputeResolutionMethod>
                                               
<reasonCode>code-code</reasonCode>
                                               
<description>text-text-text</description>
                               
</disputeResolutionMethod>
               
</variationMargin>

 

·         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

 

 

Ref: http://www.isda.org/c_and_a/pdf/Electronic-Messaging.pdf

 

Thanks, Lyteck

 


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.