|
Hi Bart,
It completely makes sense. The issue I see is that payment structures are not new in FpML. They have been there since version 1.0 and this proposal doesn't create anything new, it just reuses an existing type. So we're limited
in the amount of changes we can implement in the schema without breaking backward compatibility. Maybe a mapping table would be a good starting point to do the analysis. Is this something you could help with?
Thanks,
Marc
From: bpwg@xxxxxxxx [bpwg@xxxxxxxx] On Behalf Of Cant, Bart [bart.cant@xxxxxxxxxxxxx] Sent: Tuesday, August 10, 2010 9:33 AM To: bpwg@xxxxxxxx Cc: rptwg@xxxxxxxx Subject: FpML-BP RE: Position Report Payment report enhancement Hi Brian, Marc, Matt
Would it be worth to structure the payment information in accordance with the existing ISO20022 XML tags for payments ?
pain.001.001.03 is the iso standard for initiation of a payment. Staying in synch with standard payment tags may help in the disbursement and settlement of the transaction.
http://www.iso20022.org/catalogue_of_unifi_messages.page
Thanks
Bart ____________________________________________________ Capgemini Financial Services Global Business Unit
From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx]
On Behalf Of Marc Gratacos
See email below and attached proposal.
From: Brian Lynn [brian.lynn@xxxxxxxxxxxxxxxxxxx] Matt, Marc –
I’ve taken a crack at modeling the CME payment enhancement to the position report that we discussed over the past few meetings.
I created a new model group that covers payment details, restructured the existing PaymentMatching type to use it, and created a new PositionPayment type to hold the new structure.
I’ve attached - diagrams of the new types - a zip of the schema - a couple of examples … this first is fairly simple, the second is based on Matt’s document.
For your comments prior to wider distribution. Do I need to write up a Word doc to hold all of this stuff?
- Brian
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. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. 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. |