In ln-6 the term period is undefined. The term is not defined as an element nor a function, so it remains undefined and ambiguous. There is no element of that name in context. The rule today is: ” Context: InterestAccrualSchedule (complex type) ln-6 (Mandatory) interestRatePeriod/startDate,lenderLoanContractPeriod/startDate, interestAccrualPeriod/startDate must be equal in each period. ” There are … Continued
ln-4 refers to mlaCost which doesn’t exist in the schema. The rule today is: ” ln-4 (Mandatory) If mlaCost doesn’t exist and interestRate and margin and allInRate exist, then allInRate = margin + interestRate. “
ln-5 refers to mlaCost which is not in context. The loan today is: ” Context: InterestRatePeriod (complex type) ln-5 (Mandatory) If mlaCost and interestRate and margin and allInRate exist, then allInRate = margin + interestRate + mlaCost ” mlaCost doesn’t even exist in the schema.
ln-2 requires fixes for the missing else clause, and for the missing type of the keyword. The missing else clause is solved by adding the correct condition as per the VWG’s approved way of writing the rules. The FpML Rules when quoting a literal value have always given its type. For example cd-3 has “…must … Continued
Please add the following as a valid example for ln-1.
The MTF pointed out a missing rule that needs to be added. The issue is #97. The currency of the parValue of a Bond must be the same currency as the currency of the Bond. Due to the way this is modelled this must be captured as the parValue requires the currency to be present. … Continued
The current definition of “Backwards Compatability” is loosely defined. For the fpmlVersion attribute to work backwards compatability will need to be tightened up. 5.5 Backwards Compatibility Where possible, every attempt should be made to keep changes to the FpML schema as backwards compatible as possible. In general, the loosening of restriction, or the adding of … Continued
Looking at the proposed rule shared-18 it is apparent that the structure of 1..* parties in a message is very common and could do with refactoring into a type. Some degree of refactoring would make rules such as shared-18 much simpler. “The new rule is: ” shared-18 (Mandatory) Context: AcceptQuote (complex type), AllocationAmended (complex type), … Continued
A rule is needed to enforce disjoint dividend periods. This would prevent dividendPeriods overlapping. The new rule is: ” eqd-30 (Mandatory) Context: DividendAdjustment(complex type) Rule: Each dividendPeriod must have a disjoint unadjustedDividendPeriod from every other dividendPeriod. The unadjustedDividend period starts with the unadjustedStartDate and finishes with the unadjustedEndDate. A period is disjoint with another period … Continued
There needs to be a new rule that ensures stepDates are unique to a Step. The new rule is: ” shared-25 (Mandatory) Context: Schedule(complex type) [count(step) ge 2] Rule: step/stepDate must be unique. Comment: Each step happens on a separate date. “