Adding the rule is a good thing. I commend it.
Each “if” must have an “else” otherwise there is an unhandled situation. In this case I believe each of these “if” is more likely a “when”. i.e they should be a precondition, rather than part of the rule.
Alternatively, and even simple, to me these look like one rule.
Please could you also provide the XPath definition of the rules. The precise version makes it easier to verify.
Matthew +44 7917 596 827
DTCC’s proposal that was accepted by Eqd WG adds an optional element “numberOfValuationDates” to “EquityValuation” structure. This element explicitly tells, for example, you have “12” valuation dates instead of looking into “EquityValuation” and calculating it. (see eqd-ex23-equityOptionTransactionSupplement-index-option-cliquet.xml).
Since this “numberOfValuationDates” value is in addition to calculating it from “valuationDates” (“periodicDates” or “adjustableDates”), DTCC is proposing new business rules to make sure the values are match?
Could you please review the proposed business rules below.
Here is the
English form of validation rule for numberOfValuationDates.
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 communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.