HomeAbout FpML®SpecificationsDocumentsWorking Groups & CommitteesToolsFpML® ServicesJoin UsContact UsIssues Forum

The FpML Issues Tracker is designed to facilitate public interaction in the standard.
By registering to the Issue Tracker you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.


Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000737 [FpML] Validation Rules minor always 2008-06-06 19:39 2010-03-22 14:25
Reporter matthewdr View Status public  
Assigned To danieldui
Priority normal Resolution open  
Status assigned Target Version 4.8 First Working Draft 2010-04-16 (build 1) Product Version 4.5 Working Draft - 2008-08-29 (build 1)
Summary 0000737: ln-6 the term period is undefined
Description 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 many interpretations of this which look plausible. This will need to go back to the Loans WG to advise on the rule.
Additional Information
Tags No tags attached.
XML Tool Type
Attached Files

- Relationships

-  Notes
(0002284)
katirabh (developer)
2009-01-27 05:15

Within the scope of the InterestAccrualSchedule.

The startDate field in the FIRST element of each of the following arrays MUST be equal to each other:

- interestRatePeriod
- lenderLoanContractPeriod
- interestAccrualPeriod
(0002285)
matthewdr (manager)
2009-01-27 16:40

The proposed rule is barred by the FpML Architecture in section 2.3.9.3 "Ordering within repetitions": http://www.fpml.org/spec/fpml-arch-3-0-wd-2/html/index.html#s2.3.9.3

Reference to element()[1] (the first element) is incompatible with the FpML Architecture.
(0002295)
katirabh (developer)
2009-02-03 04:58

The accrual schedule, by its nature, is a set of (time period) contiguous set of elements that define the underlying variables for calculating an accrual.

Ideally, we would want to ensure that each of the set of elements has full coverage of dates and that each schedule starts and ends on the same set of dates.

How should we go about validating this, given the inability to order within FpML...?
(0002316)
matthewdr (manager)
2009-02-24 14:10

If you want the first date, which is defined as the earliest, then just use the min() function on the candidate set of dates. Based on the comments so far, the solution would be:

"
Context: InterestAccrualSchedule (complex type)
ln-6 (Mandatory)
(min(interestRatePeriod/startDate) eq min(lenderLoanContractPeriod/startDate)) and (min(interestAccrualPeriod/startDate) eq min(interestRatePeriod/startDate))
"
(0002318)
matthewdr (manager)
2009-02-24 15:48

Discussed at the VWG. Although the requirement was stated as "he startDate field in the FIRST element of each of the following arrays MUST be equal to each other:
", the VWG thought this needed verifying. Their expectation was that the dates must match for each period, not just the first period. There are existing examples of this that may be used.
(0002359)
matthewdr (manager)
2009-06-09 13:23

Discussed at the VWG today. This needs to verified with the Loans Working Group.

Irina will inform the Loans WG of the choices.

- Issue History
Date Modified Username Field Change
2008-06-06 19:39 matthewdr New Issue
2009-01-27 05:15 katirabh Note Added: 0002284
2009-01-27 16:40 matthewdr Note Added: 0002285
2009-02-03 04:58 katirabh Note Added: 0002295
2009-02-24 14:10 matthewdr Note Added: 0002316
2009-02-24 15:48 matthewdr Note Added: 0002318
2009-06-09 13:23 matthewdr Note Added: 0002359
2010-01-21 17:44 lyteck Target Version => 4.8 First Working Draft (Publication Date TBA)
2010-03-22 14:25 fpmladmin Assigned To PamF-W => danieldui