Please find attached an update
to the zip.. You will need to rename from
.zip-email to .zip, this is in case the zip is blocked. The changes cover
1.
Implemented the consolidation for CollateralBalance,
MarginRequirement, MarginCallResult and ExpectedCollateral (we need to work on
better names for the secondary complex types)
2.
Updated the schemaLocation attribute of the XML
examples to point to the schema folder since want to move them out of the example folder for better
visibility… this way the XML are valid as unzipped (Also I moved your 2
examples inside the \ FpML_collateral_xml folder, this way users get a
self-contained package when they unzip)
3.
Misc other changes. E.g., relax cardinality of
marginRequirement\variation to accommodate your Deliver xml example…
Thanks…
From:
owner-colwg@xxxxxxxx [mailto:owner-colwg@xxxxxxxx] On Behalf Of richard.barton@xxxxxxxxxxxxxxxx
Sent: Wednesday, May 19, 2010 8:43 AM
To: colwg@xxxxxxxx
Subject: FPML-CWG Collateral WG Meeting Minutes - May 12, 2010
Please find the minutes from the May 12
meeting. Please let me know if any points missed.
Participants
Apologies
1.
Lyteck Lynhiavu (ISDA)
2.
Nicole Joliffe (Swift)
3.
Vivian Wu (Goldman Sachs)
Notes
In this meeting we completed going through the MC1 message.
This included reviewing the remaining pieces of the MC1 message Margin Terms,
Collateral, Margin Requirements, Margin Results and Expected Collateral.
We agreed on the terminology for Collateral Held and Pending Party
References
In Margin Terms we discussed the Rounding changes required based
on the existing FpML definition of Rounding that is used for decimal places.
For Margin Requirements we looked at two options for definition
and selected the second option which was more in line with the overall
structure related to Segregated and Non Segregated Independent Amount Margin
Calls. We also agreed on the Party Reference terms
We reviewed the Expected Collateral section and discussed whether
to use a simple type and description or support the ability to define based on
the requirement type i.e. for returns reference known collateral but for
deliveries support more general type and description as the other parties
collateral holdings are not known by the calling party.
Action Items
·
Send out the draft XSD
for the MC1 message (fpml-collateral-processes.xsd in the
FpML_collateral_xml.zip file)
Next Meeting
·
Walk through MC1 XSD
to understand how the definition we have worked on to date has been translated
·
Get volunteers to help
review the existing element descriptions and provide descriptions for each
missing ones
·
Wednesday 19th May
11am ET/4pm BST
Dial
in Details:
US Dial-in:
888-481-3032
UK Toll Free: 0800 904
7961
International Dial-in: 617-801-9600
Passcode:
8682747
Attachments
·
FpML_collateral_xml.zip
·
the zip contains a working draft FpML schema
with collateral support for MC1/MC2 (fpml-collateral-processes.xsd) and valid
XML examples for MC1 (based on cleaned up doc, the values aren't realistic) and
MC2 (Rescind). This is an early draft version which needs to be reviewed
and requires optimization. It does allow people to build MC1 and variations as
agreed in the word document
This
email and any files transmitted with it are confidential and proprietary to
Algorithmics Incorporated and its affiliates ("Algorithmics"). If
received in error, use is prohibited. Please destroy, and notify sender. Sender
does not waive confidentiality or privilege. Internet communications cannot be
guaranteed to be timely, secure, error or virus-free. Algorithmics does not
accept liability for any errors or omissions. Any commitment intended to bind
Algorithmics must be reduced to writing and signed by an authorized signatory.
This
email and any files transmitted with it are confidential and proprietary to
Algorithmics Incorporated and its affiliates ("Algorithmics"). If
received in error, use is prohibited. Please destroy, and notify sender. Sender
does not waive confidentiality or privilege. Internet communications cannot be
guaranteed to be timely, secure, error or virus-free. Algorithmics does not
accept liability for any errors or omissions. Any commitment intended to bind
Algorithmics must be reduced to writing and signed by an authorized signatory.
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.
Attachment:
FpML_collateral_xml.zip-email
Description: FpML_collateral_xml.zip-email