.. taken from the text of e-mail send to ISDA … “I am looking at the changes documents for ALL the versions in 5.6. In the first of these it states, under the rules-english-ref.xml section (i.e. the Reference rules) “enabled ref-14 to 21, ref 31, ref36-37 in reporting view”. None of the subsequent changes docs … Continued
Supplement No. 22 to the 2006 ISDA Definitions, published July 2010, provides for the addition of a new Section 7.1(r)(iii) containing definitions for the PLN-POLONIA-OIS-COMPOUND rate. Please see http://www.isda.org/publications/pdf/Supplement-No-22-to-2006Defs.pdf for the full supplement. As a result a new value needs to be added to the floating-rate-index scheme: Value: PLN-POLONIA-OIS-COMPOUND Source: ISDA Description: Per 2006 ISDA … Continued
Confirmation View The downloadable documentation includes the Loan rules. There are no loan related schemas in the confirmation (view (or in fact any of the 5 views). This is a little misleading !
Confirmation View Some of the contexts to which shared-5 is to be applied don’t appear to be present in the confirmation view ? PaymentMatching PhysicalLeg PrincipalMovement QutablePayment
The invalid test case for rule ref-30 does not parse. There is no valid test case for ref-30.
The invalid test case for rule ref-10 does not parse. There is no valid test case for ref-10.
ABS Benchmarks Administration Co Pte. Ltd. (ABS Co), in consultation with the Singapore Foreign Exchange Market Committee (SFEMC), announced Feb 18 that it will discontinue the USD/IDR spot rate benchmark (denoted as IDR VWAP or IDR03 in the 1998 FX and Currency Option Definitions). The last day of publication of IDR VWAP (IDR03) will be … Continued
Capitalise the initial F ! I think the [ecore:reference=”floatingRateCalculation”] should be [ecore:reference=”FloatingRateCalculation”] in order to refer to the type, rather than the element.
Should documentation be [can’t] instead of [can] ? That is, you use an account reference here when you _can’t_ distinguish which account to use from the party reference alone, such as an inter-book trade.
I’d like to have the schema published for each view, * merged into one file * stripped of comments (which should be for devs, not users) * including annotation/documentation (which is for users) * sorted by kind, then name, with global elements first. Benefits: * Easier to find item in a single schema with documentation … Continued