FpML-AWG FW: Deployed class names

Hi Marc,

Apologies for the delay in getting back to you.

The answer is broadly “yes” … but here is the more detailed answer provided by someone who understands a lot more about the nuts and bolts than I do.

“there are classes for types and elements and yes their names gets derived from what they are called in the model”

I hope that clarifies.

Regards

Pam

From: Marc Gratacos [mailto:MGratacos@xxxxxxxx]
Sent: Thursday, November 12, 2009 14:40
To: Pamela Webber-Cooke
Subject: RE: Deployed class names

Hi Pam,

Just to clarify, I assume classes are being deployed using the type names as, for example, Trade.CreditDefaultSwap.GeneralTerms.InitialPayment.XXX. is that right?

Thanks,

Marc

From: Pamela Webber-Cooke [pwebber@xxxxxxxxxxxx]
Sent: Thursday, November 12, 2009 11:44 AM
To: Marc Gratacos
Subject: Deployed class names

Hi Marc,

I have been asked to draw the following to ISDA’s attention. I am not too sure to whom I should address this but I am sure that you can forward it on appropriately if required.

We are currently working on a number of the FpML upgrades and have noticed that the deployed class names (clearly derived from the FpML structure) are now becoming very close to the 256 character limit that is imposed by Windows. If the structure of the schemas becomes any “deeper” in later versions this limit will be passed which will cause serious implementation issues on Windows platforms.

I’d be grateful to receive any feedback you may have on this.

Regards

Pam

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.