The current timeframe for publication of
the second trial recommendation of 4.4 is this coming Wednesday. If you have any
questions or concerns about the support for fixed recovery swaps, it’s
best if you raise them by early next week.
Thanks and have a great weekend,
Ben Lis
Head of Product Management &
Integration
T-Zero
212.323.6041
www.tzero.com
From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx]
On Behalf Of Irina Yermakova
Sent: Wednesday, June 25, 2008
11:12 AM
To: cdwg@xxxxxxxx
Subject: RE: FpML-CD Adding
support for Fixed Recovery Swaps -- Call for Comments Closes Monday, June 23rd
Please review the attached schema zip file (to unzip the
attachment, first rename it from xml.doc to xml.zip) that holds the changes for
the fixed recovery factor support (fpml-cd-4-4.xsd) and an example
(cd-ex16-short-us-corp-fixreg-recovery-factor.xml).
Thank you,
Irina Yermakova
From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx]
On Behalf Of Ben Lis
Sent: Wednesday, June 18, 2008
10:31 AM
To: cdwg@xxxxxxxx
Subject: RE: FpML-CD Adding
support for Fixed Recovery Swaps -- Call for Comments Closes Monday, June 23rd
We discussed support for Fixed Recovery
Swaps on today’s CDWG call.
The consensus on that call was that we
should move forward in an expedited manner with the proposal that Jamie has
submitted to the CDWG (see first mail on the stream below). To the point that
Henri raises, the consensus of the members on the call was to go with option
(1) making it explicit in the annotation that the currency will be derived from
the Floating Rate Payer Calculation Amount.
Pending Coordination Committee approval,
we will publish this change out in the second trial recommendation of FpML 4.4
If you have outstanding questions or
concerns on the proposal for adding support for Fixed Recovery Swaps, please
raise them on this e-mail stream before close of business Monday, June 23rd
2008. If no unaddressed concerns are raised by this time, we will move forward
with this change.
Thanks,
Ben Lis
Head of Product Management &
Integration
T-Zero
212.323.6041
www.tzero.com
From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx]
On Behalf Of Henri Pegeron
Sent: Tuesday, June 10, 2008 10:03
PM
To: cdwg@xxxxxxxx
Subject: Re: FpML-CD Adding
support for Fixed Recovery Swaps
Jamie,
This proposal looks good - DTCC has also gotten feedback that CDS Recovery
Swaps will need to be supported in FpML and this field would allow users to
submit confirms with a fixed recovery as opposed to an explicit cash settlement
amount.
One comment I have is around the existing "currency" component of the
cashSettlementAmount. Right now, FpML is allowing the
cashSettlementAmount to have a currency that is different than that of the
Notional amount. If we allow a choice between the amount or a fixed recovery
factor, we should consider either:
- making it explicit in the annotation that the
currency will also be derived from the Floating Rate Payer Calculation
Amount.
- making "recoveryFactor" a complexType
and include both the rate and the currency.
I believe option one would be easier
to implement and probably less contentious (since the 2nd would involve making
or reusing a type).
Any
thoughts?
Regards,
Henri Pegeron
------------------------------------------------------------
The Depository Trust & Clearing Corporation
DTCC Deriv/SERV : Business Analysis & Design
55 Water Street
- New York, NY 10041
Phone: + 1 (212) 855 1682
Fax: + 1 (212) 855 1020
|
"Orme, Jamie"
<Jamie.Orme@xxxxxx>
Sent
by: cdwg@xxxxxxxx
06/10/2008
03:44 PM
|
Please respond
to
cdwg@xxxxxxxx
|
|
|
To
|
<cdwg@xxxxxxxx>
|
|
cc
|
|
|
Subject
|
FpML-CD Adding support for Fixed Recovery Swaps
|
|
CDWG,
We would like to update the creditDefaultSwap
schema to fully support Fixed Recovery swaps.
Currently the cashSettlementTerms
only allows for Fixed Recovery where an amount is specified:
<cashSettlementTerms>
<cashSettlementAmount>
<currency>USD</currency>
<amount>1500.0</amount>
</cashSettlementAmount>
</cashSettlementTerms>
We would like to extend this so that a "recovery factor", if
applicable, could be included instead. The factor is a fraction that will
then be used to calculate the amount of recovery on a Credit Event.
Within our paper flows, we currently confirm this as follows:
1.Settlement Terms:
Terms Relating to Cash Settlement:
Settlement Method: Cash Settlement
Settlement Currency: The currency of denomination of the Floating Rate Payer
Calculation Amount
Recovery Factor [0.50]
Cash Settlement Amount (1 minus the Recovery Factor) multiplied by the Floating
Rate Payer Calculation Amount
Therefore, we propose to use a new 'FixedRecovery.model'
group that will provide a choice between a fixed settlement amount or a
recovery factor:

Based
on our confirm "snippet", this would then be modelled in FpML as
follows:
<cashSettlementTerms>
<recoveryFactor>0.5</recoveryFactor>
</cashSettlementTerms>
To see this change in context, please see the attached schema change.
Could we get together to discuss the above?
Many
Thanks
Jamie
________________________________________________________
DTCC DISCLAIMER: This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error, please notify us
immediately and delete the email and any attachments from your system. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email.
**************************************************************************************************************************
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 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.
**************************************************************************************************************************