The definition of Interval contains a period element of type “PeriodEnum”. One value of PeriodEnum is “T”, which represents Term. The term that is being referred to is dependent upon the context in which it is referred to. For this WG the task is to define the term for those parts of the schema owned … Continued
The definition of Interval contains a period element of type “PeriodEnum”. One value of PeriodEnum is “T”, which represents Term. The term that is being referred to is dependent upon the context in which it is referred to. For this WG the task is to define the term for those parts of the schema owned … Continued
The definition of Interval contains a period element of type “PeriodEnum”. One value of PeriodEnum is “T”, which represents Term. The term that is being referred to is dependent upon the context in which it is referred to. For this WG the task is to define the term for those parts of the schema owned … Continued
Following the last VWG Pam asked me to raise an issue for this. The question had already been put to Harry, who may respond. FpML defines an Interval using a period of type PeriodEnum. One of the values of PeriodEnum is “T”, which is short for “Term”. When I see the Interval contains a Term … Continued
Issue reported by Matthew Rawlings VWG 2009-01-27: In FpML, Interval is used to represent Duration and Frequency. FpML also defines a Schedule as a kind of Interval with CommodityCalculationPeriodsSchedule. There are also offsets and frequencies. We should be consistent with terms around “Interval”, “Duration”, and “Schedule”.
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