FpML-AWG FW: Updated schema for loans

To: <awg@xxxxxxxx>

Subject: FpML-AWG FW: Updated schema for loans

From: "Marc Gratacos" <MGratacos@xxxxxxxx>

Date: Thu, 6 Sep 2007 07:15:29 -0400

Importance: normal

Reply-to: awg@xxxxxxxx

Sender: awg@xxxxxxxx

Thread-index: Acfdx4Kqv3JkOFYuRNWK/OYapnIB3wMeaHKAAY1bGRA=

Thread-topic: Updated schema for loans

Title: Updated schema for loans

For item 2 of the agenda:

When the Credit Event Notice was created, there was a suggestion to use of a substitution group to indicate the credit events applicable to the notice instead of optional empty elements. In some cases the elements that belong to the substitution are empty elements. They create a flag when they appear at the document.

…

<entityName>Solutia Inc.</entityName>

</referenceEntity>

<bankruptcy/>

…

The Commercial Loan Working Group is trying to create a similar structure for loan notices and there is a question on the group whether the use of substitution groups in this case (for loan events) it is still the preferred approach.

From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx] On Behalf Of oleg.starovoitov@xxxxxxx
Sent: Wednesday, August 29, 2007 12:02 PM
To: Bhavik.Katira@xxxxxxx; loanwg@xxxxxxxx
Cc: James-W.Smith@xxxxxxx; Brian.Powers@xxxxxxx
Subject: Updated schema for loans

Hi,
I made few updates to the schema following our meeting discussion:
1. Moved enums and top-level notice message to the top of the file to simplify navigation - schema layout pending off-line review with Pierre

2. Added back FxTerms type - pending confirmation from the business group
3. Completed OngoingFee notice design - pending review with Bhavik. I applied changes we discussed during the meeting, here are differences with business spec:

- removed fxRatePeriod section, we agreed it will not be needed as all position levels for calculations will be provided in the base facility currency

- removed LC fee section, we agreed it will be separate notice
4. Renamed old LenderPositionPeriod into LenderLoanContractPeriod - as Ongoing Fee Notice introduces another LenderPositionPeriod type

5. Replaced loanContractNotice and facilityNotice substitution groups with choice - it allows to have the same XML but much simpler, shorter and less naming issues - pending Mark review with architecture group.

6. Removed word 'Document' from the type names - positive side-effect of removing substitution groups
7. Updated sample to comply with new schema.

Irina, please submit new schema in the source control.

Please, send me any comments/suggestions.
Regards,
Oleg.
<<fpml-loan.xsd>> <<DrawdownNoticeSample.xml>>

************************************************************************************************************************** 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 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-loan.xsd
Description: fpml-loan.xsd

Attachment: DrawdownNoticeSample.xml
Description: DrawdownNoticeSample.xml

Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.