FpML Issues Tracker

609: Interval should be replaced with xs:duration

February 29, 2008

closed

Minor

Always

Architecture

Admin

andrew

Summary

The Interval definition in fpml-shared.xsd is equivalent to the built in xsd:duration. There is much better support in tools for xsd:duration than there is for Interval, which needs to be parsed back into a duration by people using the Interval.

I propose replacing the use of Interval with xsd:duration.

Interval is defined as:

A type defining a time interval or offset, e.g. one day, three months. Used for specifying frequencies at which events occur, the tenor of a floating rate or an offset relative to another date. A time period multiplier, e.g. 1, 2 or 3 etc. A negative value can be used when specifying an offset relative to another date, e.g. -2 days. If the period value is T (Term) then periodMultiplier must contain the value 1. A time period, e.g. a day, week, month, year or term of the stream. If the periodMultiplier value is 0 (zero) then period must contain the value D (day).

Notes:

  • andrew

    02/29/08 4:09 pm

    The functionality of schema’s duration type does not match the features of FpML’s Interval, in particular the period lengths of ‘Week’ and ‘Term’ (which refers to time period between the effective and termination dates) are not supported without loss of business meaning.

    I don’t think we can make this change.

  • matthewdr

    02/29/08 4:38 pm

    Withdrew issue following feedback from AJ clarifying the type.

  • Leave an update

    You must be logged in to post an update.