RE: FpML-CD Add entityType for Single Name CDS

Title: Add entityType for Single Name CDS

Following on from the below, I have spoken with Karel Engelen from ISDA and he has raised some interesting points about this proposal.

For both single name CDS and baskets, the information carried by Entity Type could instead be modelled using Documentation->contractualMatrix->matrixTerm (with values from the matrixTermScheme).

Having the ability to specify the same information in two different places could lead to inconsistencies. From what I can gather this has been discussed before. Maybe this is a good opportunity to determine once and for all where this information should go strategically? We could then deprecate the other approach if necessary.

Another point was raised about moving entityType into LegalEntity. Believe that this construct is used elsewhere in the schema. Given the current annotation of entityType does it make sense for it to be present outside of the context decribed below?

If we could discuss this further at the next WG meeting I'd be very grateful.

Thanks

Jamie

From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx] On Behalf Of Ben Lis
Sent: Wednesday, June 18, 2008 3:45 PM
To: cdwg@xxxxxxxx
Subject: RE: FpML-CD Add entityType for Single Name CDS

On today’s CDWG call the general consensus was that we should move forward with this proposal. Andrew Parry suggested a modeling change – making entityType an optional element of LegalEntity. He will circulate this proposal for further comment.

Ben Lis

Head of Product Management & Integration

T-Zero

212.323.6041

www.tzero.com

From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx] On Behalf Of Orme, Jamie
Sent: Tuesday, June 10, 2008 8:13 PM
To: cdwg@xxxxxxxx
Subject: FpML-CD Add entityType for Single Name CDS

CDWG,

Currently entityType is only available for Basket Swaps (see basketReferenceInformation->referencePool->referencePoolItem->referencePair).

We would now like to add entityType to the schema for single names as well.

The annotation for entityType is as follows:

"Defines the reference entity types corresponding to a list of types in the ISDA First to Default documentation."

From speaking to our documentation team they use this information to ensure the appropriate annexes (detailing applicable Credit Events, etc.) are added to the long form confirm for each reference entity type within the basket.

We would now like to add the same facility for single names. This will be especially useful where the reference entity cannot be easily classified from the information currently available in the schema.

For consistency with current Basket Swap implementation, we propose that entityType should be added to the referenceInformation element that is within the generalTerms of the creditDefaultSwap schema.

Please see the attached diagram detailing the updated referenceInformation element and the modified schema:

<<entityType.png>> <<fpml-cd-4-4.xsd>>
Could we get together to discuss whether or not this modification to the schema can be formally adopted?
Many Thanks
Jamie