Message Recall Failure: Recall: FpML-CD Proposals: STS Calc Agent Hardcoding / IOS and PrimeX STS values

Henri,

Item #2 is implemented as proposed. This was agreed at the Jan-11-2010 Standards Committee call.

Regards,

Irina Yermakova

From: cdwg@xxxxxxxx [mailto:cdwg@xxxxxxxx] On Behalf Of Henri Pegeron
Sent: Monday, January 25, 2010 3:35 PM
To: cdwg@xxxxxxxx
Subject: RE: FpML-CD Proposals: STS Calc Agent Hardcoding / IOS and PrimeX STS values

Marc/Ben,

Any update on the approach here for item #2? The industry has agreed that defaulting to the STS for Calculation Agent should be denoted on the confirm. Since a similiar approach was taken for MCA's should FpML add a value to support the default when a Standard Terms Supplement is used?

The first STS to use this feature goes live in one month ("IOS") so we need to know the approach that will be used asap.

Thanks,

- H

Henri Pegeron

Vice President
Business Analysis and Platform Integration

MarkitSERV

55 Water Street, 22nd Floor
NY, NY 10041
+1 212 855 1682 Office
+1 212 855 1020 Fax

henri.pegeron@xxxxxxxxxxxxxx
www.markitserv.com

From: cdwg@xxxxxxxx on behalf of Ben Lis
Sent: Thu 12/31/2009 5:59 PM
To: cdwg@xxxxxxxx
Subject: Re: FpML-CD Proposals: STS Calc Agent Hardcoding / IOS and PrimeX STS values

Hi Henri:

I think it may make most sense to consider your email as two separate proposals:

1. Addition of IOS and PrimeX STS values to Contractual Supplement Scheme
2. Calc Agent hard coding

I support 1 and second your proposal.

I'll defer to Marc Gratacos on item 2, but I believe our principle is that a data element that is specified in an STS, matrix or MCA does not appear in the equivalent FpML doc.
Following this principle, the calc agent element would not appear in the document.

Best wishes to you and all the CDWG members for a happy and healthy 2010.

Thanks,
Ben

----- Original Message -----
From: cdwg@xxxxxxxx <cdwg@xxxxxxxx>
To: cdwg@xxxxxxxx <cdwg@xxxxxxxx>
Sent: Mon Dec 28 17:35:43 2009
Subject: FpML-CD Proposals: STS Calc Agent Hardcoding / IOS and PrimeX STS values

Ben/All,

Through discussions with legal and the industry, there is a trend in recently drafted documents moving towards hardcoding the Calculation Agent into Standard Terms Supplements rather than having it as a confirmable field. Firms would provide this on their FpML submissions similarly to "AsSpecifiedInMasterAgreement" for MCA's. This was most recently seen on the TRX template, and based on the feedback I've received from clients, will also be present on the upcoming "IOS" and "PrimeX" Standard Term Supplements as well.

In preparation for this I'd like to propose that a new value for Calculation Agent be added to the enumeration list for the <calculationAgentParty> element:

AsSpecifiedInStandardTermsSupplement'
The Calculation Agent is determined by reference to the relevant standard terms supplement.

For the two new Supplements coming in January, I'd also like to propose adding two new values to the http://www.fpml.org/coding-scheme/contractual-supplement <http://www.fpml.org/coding-scheme/contractual-supplement> (contractual supplement scheme) of:

IOS
Standard Terms Supplement for IOS transactions

PrimeX
Standard Terms Supplement for PrimeX transactions

As noted above, these two supplements would likely need the 'AsSpecifiedInStandardTermsSupplement' value in order to confirm properly in FpML. I'd appreciate it we could discuss both items at the next CDWG.

Regards,

Henri Pegeron
Vice President
Business Analysis and Platform Integration

MarkitSERV

55 Water Street, 22nd Floor
NY, NY 10041
+1 212 855 1682 Office
+1 212 855 1020 Fax
henri.pegeron@xxxxxxxxxxxxxx <mailto:henri.pegeron@xxxxxxxxxxxxxx>
www.markitserv.com <http://www.markitserv.com/>

-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe cdwg youremail@address
To view archives: http://www.fpml.org/_wgmail/_cdwgmail/threads.html

This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

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.