Issue reported by Matthew Rawlings VWG 2009-01-27: The value ‘T’ (term) within the PeriodEnum is business correct, but I believe the XSD isn’t. TERM isn’t really a period, but a reference to a period elsewhere. A schema change to make that clear would help greatly. I would define an Interval as a choice of a … Continued
The introduction of the element within in FpML 4.4 has made that all short-form examples with recovery factor don’t pass rule cd-21 since the rule says “If the condition ShortForm is true, and if the condition SingleName is true, then the following elements must not exist: cashSettlementTerms, […]”
The Business Day Convention has a value of “NotApplicable” in the enumeration. In other cases of a value being not applicable we have either omitted the element entirely, rather than add it and then add content to say it is not applicable. For the sake of consistency and simplicity of processing, please consider this case.
The Business Day Convention uses the term “NONE”. I suggest in the next change when we can make a non-backwards compatible change that it is changed to “ACTUAL”. IMHO The term “ACTUAL” has better support in the industry for date rolling conventions. This also avoids confusion with the other enumeration value of no convention of … Continued
The definition of NEAREST in FpML is: “The non-business date will be adjusted to the nearest day that is a business day – i.e. if the non-business day falls on any day other than a Sunday or a Monday, it will be the first preceding day that is a business day, and will be the … Continued
Given the current market conditions, we expect to hit zero or negative interest rate situations. Just wanted to give a heads up to make sure that we look for places where this could cause an issue – so far I have only seen ird-25 rule, which currently applies to fixedRateSchedule ( when there are no … Continued
The precise description of shared-9 should be: ” iff(not exists(businessCentersReference|businessCenters), businessDayConvention = (“NONE”, “NotApplicable”)) “
shared-1 rule is: ” iff(exist businessCentersReference or businessCenters, businessDayConvention ne “NONE” or “NotApplicable”) ” This is illegal XPath. The rule should be: ” iff(exists(businessCentersReference|businessCenters), not(businessDayConvention = (“NONE”, “NotApplicable”))) “
Many of the Validation Examples are schema invalid. It looks like a problem with masterAgreementVersion under masterAgreement. This is in the validation-rules branch. The warnings I get from XML Spy are: File C:workingganny-wsvalidation-rulessrcvalidationexamplesvalid-testcasesvalid-cd-1-01.xml is not valid. Element is not allowed under element . Reason: The following elements are expected at this location (see below) Annotations … Continued
Please add the following for the ISDA1999Creditr precise description of the PreCondition: ” some $document in (//element(*, Trade)|//element(*, Contract))/documentation/(contractualDefinitions|masterConfirmation/masterConfirmationType) satisfies contains($document, “ISDA1999Credit”) “