FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
None
Summary
ird-57 should use the approved mathematical notation in the FpML Validation Architecture. It at least needs aligning with ird-58.
The rule today: " ird-57 (Mandatory) Context: CalculationPeriodFrequency (complex type) [isParametric] [rollConvention != ("NONE", "SFE", "MON", "TUE", "WED", "THU", "FRI", "SAT","SUN")] period must be M or Y. "
The proposed resolution: " ird-57 (Mandatory) Context: CalculationPeriodFrequency (complex type) [isParametric] [rollConvention != ("NONE", "SFE", "MON", "TUE", "WED", "THU", "FRI", "SAT","SUN")] period = M or Y. "
When we say "M or Y" we're trying to say there is a set of PeriodEnums that contains "M" and "Y" and the period element's value must be in that set. My concern is that "M or Y" does convey clearly the concept of a set. The definition of "=" as a comparator on a set is undefined.
The XPath way of defining this would be: " ird-57 (Mandatory) Context: CalculationPeriodFrequency (complex type) [isParametric] [rollConvention != ("NONE", "SFE", "MON", "TUE", "WED", "THU", "FRI", "SAT","SUN")] period = ('M'. 'Y') "
My concern is that my colleagues have interpreted "period = M or Y." as being equivalent to a boolean OR on the values "M" and "Y", followed by an EQUALS against the value of period. Basically, the terms need to be defined if we don't use the pre-defined XPath terms.
Notes:
lyteck
10/07/08 1:36 pm
ValWG 2008-10-07: implement throughout and keep original English wording as comment (similar to what was agreed in 811)
(note: in this example, M and Y should be quoted)
lyteck
10/08/08 2:42 pm
changed ird-57: to period=(“M”,”Y”) + comment
Scanned all rules and didn’t find any other similar instances to change. Closing the issue.
matthewdr
10/08/08 2:42 pm
Closing after testing.
matthewdr
10/08/08 2:43 pm
Closed after testing.