|
Jamie, Looking at the legal documentation, the
entity type for FTD baskets has exactly the same role as the transaction type
for the matrix or the MCA’s. It has been suggested in the legal groups
that this should be standardized and that the FTD elections should be the same as
the matrix transaction types. There seems to be agreement on the principle but
it was never prioritized on the legal side. By introducing entity type for single
names ( and leaving the current differences aside given the intent to harmonize
that at one point) you would duplicate the information already available in the
transaction type. Why not use the transaction type instead? Karel From: cdwg@xxxxxxxx
[mailto:cdwg@xxxxxxxx] On Behalf Of Orme,
Jamie 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 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>> |